You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you run a command with parallelization it uses all of the CPU cores, which puts a higher than wanted load on our QA server that is already running builds for multiple environments in parallel at the Docker level (outside the scope of Robo).
Expected behavior
When you run a command with parallelization you can specify how many cores you want to use.
Actual behavior
I am unable to specify the number of cores I want to use.
System Configuration
This is all likely N/A to this issue, but I'm providing it anyways
Yes, a PR would be welcome. I am not sure off the top of my head how resource limitations can be specified in ParallelExec. Adding setters to tasks is straightforward, though, so as long as you have a mechanism to enforce the limits you want, this should be straightforward to do.
Steps to reproduce
When you run a command with parallelization it uses all of the CPU cores, which puts a higher than wanted load on our QA server that is already running builds for multiple environments in parallel at the Docker level (outside the scope of Robo).
Expected behavior
When you run a command with parallelization you can specify how many cores you want to use.
Actual behavior
I am unable to specify the number of cores I want to use.
System Configuration
This is all likely N/A to this issue, but I'm providing it anyways
Proposed Change
I assume such a change would be done in
ParallelExec::run
, presumably via a new property on the class with a setter method?The text was updated successfully, but these errors were encountered: