[SERVER-51251] Increase parallelism in Evergreen tasks Created: 30/Sep/20 Updated: 29/Oct/23 Resolved: 02/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Raiden Worley (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | STM 2020-10-19 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
When switching from c4 to m4 instances of similar memory sizes (but with fewer CPUs), we're seeing similar task runtimes with the same level of parallelism in one-off patch builds. We'd like to be able to change the resmoke job factor on a per-distro basis. For m4, we will set it to 1.618 instead of 1, which is the default now . The job factor will apply to Enterprise RHEL 6.2 and Linux DEBUG and will be a change in evergreen.yml. The job factor will be changed in evergreen_resmoke_job_count.py |
| Comments |
| Comment by Githook User [ 02/Oct/20 ] |
|
Author: {'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}Message: |