[SERVER-46437] Create a baseline build variant to understand task splitting overhead Created: 26/Feb/20 Updated: 29/Oct/23 Resolved: 13/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | DAG 2020-04-06, DAG 2020-04-20 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
It would be nice to have a way to understand the overhead associated with splitting up tasks into subtasks. This would allow us to watch any runtime issues that might be hidden by splitting up a task (e.g. large test runtime increases being masking by more aggressive splits of the tests). It would also help us understand if and where there are opportunities for improvements in task splitting. One way to accomplish this would be to have a build variant that mimics a standard build variant, but without splitting the tasks. We wouldn't need to run the task frequently, once a week would likely be enough. As a Dev Prod engineer, AC:
|
| Comments |
| Comment by Githook User [ 13/Apr/20 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: |
| Comment by Cristopher Stauffer [ 26/Feb/20 ] |
|
LGTM |