Block parallel Eclipse runs when NUM_CPU is set to 1
Open
- Dominant language
- Python
- Stars
- 161
- Forks
- 140
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 138
Description
Logging reveals that there is a lot of simulations every week where NUM_CPU is set to 1 but Eclipse still runs in parallel.
These users get a warning post-simulation, but this turns out not to be sufficient.
One should explore possibilities for blocking this, as this anti-pattern steals CPU-resources from other users, and gives users a much lower pending time that what is correct.
Contributor guide
Research direction
No files or tests are named. Start by locating the code that handles NUM_CPU and Eclipse parallel execution, then inspect the existing post-simulation warning. Done means simulations with NUM_CPU set to 1 cannot run Eclipse in parallel, with the behavior covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100