Hi ElegantCoyote26 , this is actually supported in the command line options for the services agent (the agent monitoring the services queue). In the command line, instead of --services-mode use --services-mode <max-num>
I am tagging AgitatedDove14 since I sort of need an answer asap...!
in particular, I ran the agent with clearml-agent daemon --queue test-concurrency --create-queue --services-mode 2 --docker "ubuntu:20.04" --detached and enqueued 4 tasks to it that sleep 15 minutes.
I can see all 4 tasks running, see
i expected to see 2 tasks running, and then when completed the remaining 2 could start. Is this not the expected behavior?
Hi SuccessfulKoala55 I am having some issues with this. I have put a concurrency limit of 2 and I can see 3 workers running
Can you share the agent's log? It will create a log file the temp folder (when started in detached mode it should output the log file in stdout)
That's realty strange - this might be a bug? What agent version are you using?
Can you perhaps try upgrading to the latest official release (I think it's 1.3.0)?
Hi ElegantCoyote26 , in theory no limit, but that depends on how you spined the services queue agent:
https://clear.ml/docs/latest/docs/clearml_agent/clearml_agent_daemon
See services mode :
To limit the number of simultaneous tasks run in services mode, pass the maximum number immediately after the
--services-mode
option (e.g.
--services-mode 5
)
Right, I used --services-mode 2 and it still runs more than 2 tasks simultaneously