[SERVER-26224] Resmoke gets much slower with more parallelism Created: 21/Sep/16 Updated: 06/Dec/17 Resolved: 27/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Eddie Louie |
| Resolution: | Done | Votes: | 1 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: |
yields: All 28 test(s) passed in 200.13 seconds,
yields: All 28 test(s) passed in 22.45 seconds. |
||||||||||||
| Sprint: | TIG 2017-04-17 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
With -j24 test suites now take at a minimum 200 seconds to execute, while some used to run in about 5 seconds. This slows down development and probably adds to CI costs. The following fixes it:
With this,
yields: All 28 test(s) passed in 5.41 seconds. |
| Comments |
| Comment by Githook User [ 27/Mar/17 ] |
|
Author: {u'username': u'elouie99', u'name': u'Eddie Louie', u'email': u'eddie.louie@mongodb.com'}Message: |
| Comment by Max Hirschhorn [ 21/Mar/17 ] |
|
I'm hesitant to lessen or remove altogether the staggering of resmoke.py jobs until we better understand the system resource utilization of our test suites. What I'd like to do for this ticket for now is to add a new --stagger-jobs flag to resmoke.py that defaults to being off and only enable it in Evergreen. This way local testing won't be impacted by this issue. |
| Comment by Eric Milkie [ 21/Sep/16 ] |
|
I think "10" in the sleep is too much. Perhaps "1" or "2" would be sufficient. |