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
Answered
Is There A Way To Get A Task'S Docker Container Id/Name? I'M Generally Interested In Resource Profiling Of Each Container, So I Noticed I Can Use

is there a way to get a Task's docker container id/name? I'm generally interested in resource profiling of each container, so I noticed I can use docker stats . I know a Task's results page also has a plot for this, but I guess it's at the machine level and not the task level?
Any ideas? I'd like to know how much memory/cpu/disk space/etc each one of my tasks take

  
  
Posted 2 years ago
Votes Newest

Answers 11


For a hacky way you can do docker ps and see the docker run command. I believe it contains the task id, so you can grep by task id

  
  
Posted 2 years ago

Yeah, that would be nice!

  
  
Posted 2 years ago

um, this line is not doing anything for me 🤔
controller_clearml_task = Task.current_task() controller_clearml_task.set_resource_monitor_iteration_timeout( seconds_from_start=10 )

  
  
Posted 2 years ago

Hi ElegantCoyote26

is there a way to get a Task's docker container id/name?

you mean like Task.get_task("task_id_here").get_base_docker() ?

ow a Task's results page also has a plot for this, but I guess it's at the machine level and not the task level?

This is actually on the container level, meaning checked from inside the container. It should be what you are looking for

  
  
Posted 2 years ago

Oh, yes, that might be (threshold is 3 minutes if no reports) but you can change that:
task.set_resource_monitor_iteration_timeout(seconds_from_start=10)

  
  
Posted 2 years ago

I see, ok!
I will try that out.
Another thing I noticed: none of my pipeline tasks are reporting these graphs, regardless of runtime. I guess this line would also fix that?

  
  
Posted 2 years ago

AgitatedDove14 I noticed a lot of my tasks don't contain these graphs though...

  
  
Posted 2 years ago

they are taking longer than 30 secs, but admittedly not much longer: 1-3 minutes

  
  
Posted 2 years ago

none of my pipeline tasks are reporting these graphs, regardless of runtime. I guess this line would also fix that?

Same issue, that said, good point, maybe with pipeline we should somehow make that a default ?

  
  
Posted 2 years ago

ElegantCoyote26 could be, if the Task run is under 30sec?!

  
  
Posted 2 years ago

I have this inside my pipeline defined with decorator

  
  
Posted 2 years ago
1K Views
11 Answers
2 years ago
one year ago
Tags