[SERVER-33147] Limit the -j/num_jobs_available for high core ARM CI servers Created: 06/Feb/18 Updated: 29/Oct/23 Resolved: 12/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.14, 3.6.3, 3.7.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Zakhar Kleyman | Assignee: | Zakhar Kleyman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.6, v3.4
|
||||
| Participants: | |||||
| Description |
|
We use $(grep -c ^processor /proc/cpuinfo) as the -j/num_jobs_available value for ubuntu1604-arm64 distros right now. We should do it in such way that this would work on both new and old servers. |
| Comments |
| Comment by Githook User [ 12/Feb/18 ] |
|
Author: {'email': 'zakhar.kleyman@mongodb.com', 'name': 'Zakhar Kleyman', 'username': 'zakhark'}Message: |
| Comment by Githook User [ 12/Feb/18 ] |
|
Author: {'email': 'zakhar.kleyman@mongodb.com', 'name': 'Zakhar Kleyman', 'username': 'zakhark'}Message: |
| Comment by Githook User [ 12/Feb/18 ] |
|
Author: {'email': 'zakhar.kleyman@mongodb.com', 'name': 'Zakhar Kleyman', 'username': 'zakhark'}Message: |
| Comment by Zakhar Kleyman [ 06/Feb/18 ] |
|
Thanks, max.hirschhorn I was thinking of doing something like |
| Comment by Max Hirschhorn [ 06/Feb/18 ] |
|
zakhar.kleyman, you could consider setting the ${max_jobs} expansion as a way to define a hard limit on the maximum number of tests that resmoke.py will run concurrently on the ARM machine. |