[SERVER-26456] Avoid overloading Windows test machines Created: 04/Oct/16 Updated: 04/Oct/16 Resolved: 04/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | DO NOT USE - Backlog - Test Infrastructure Group (TIG) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
This "sharding" task, for example, ran on a Windows Debug host with 32 concurrent jobs: Even with the staggering test starting (which staggers successive job starts by 10 seconds, but only after the first five jobs have started simultaneously), running this number of jobs on one machine will still overwhelm the IO subsystem. |