Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Unanswered
Hello. I'M Running The Self-Hosted Version Of `Clearml-Server` And I'M Seeing That The Elasticsearch Container Is Using A Lot Of Memory. I Have Two Questions: 1. Would Archiving Old Experiments Help Reduce The Memory Usage Of The Elasticsearch Container?


Hi @<1778231475670355968:profile|PompousTurtle5> , I'm afraid that since Elastic runs as a container this is configured at the docker-compose and passed directly. On what hardware is your server running? How many jobs do you run roughly in parallel? How many experiments are there?

Also to answer your questions:

  1. Would archiving old experiments help reduce the memory usage of the elasticsearch container?
  • I don't think archiving experiments would change something elastic wise, at least nothing I found in the code. 2. What would be best practice to setting a memory limit for the elasticsearch container?
  • I think that might depend on the use case and load on the system. See my questions above.
  
  
Posted 8 months ago
129 Views
0 Answers
8 months ago
8 months ago