[SERVER-66136] Should limit concurrency to nCores+2 when icecream isn't enabled Created: 03/May/22 Updated: 27/Oct/23 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Participants: |
| Description |
|
When icecream is disabled we are imposing an artificial limit of just processors, presumably to protect against people getting used to using something like -j500 melting their machine when all compiles are run locally. However, ninja by default uses processors + 2 when no -j flag is passed. I think we should change our cap to be at least this high rather than overriding ninja's default. |