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
Hi, I Would Like To Know From You, Maybe Someone Has Encountered The Problem That After Deploying An Agent Inside Docker, The Launch Of The Script Itself Occurs With A Delay (Lunch Pipeline Component). I Run Pipelines And Component Should Works Quickly, B


CostlyOstrich36 Hi,
I have a question related to ClearML’s indexing mechanism for cached datasets. We noticed that when storing the dataset cache folder on an NFS (Network File System), running the command clearml-data get triggers a cache indexing process, which takes a significant amount of time. However, if we remove the NFS cache folder, the command runs almost instantly.
Could you explain how caching works in ClearML? Specifically:

  • Why does ClearML perform global folder indexing before the script starts?
  • Why does it index the dataset cache folder when executing clearml-data get ?
  • Is there an option to disable cache indexing or control its behavior to optimize performance, especially when using NFS?Any insights or workarounds to speed up the process would be greatly appreciated.
    Thanks!
  
  
Posted one month ago
21 Views
0 Answers
one month ago
one month ago