[SERVER-43158] Reduce frequency of sys-perf on non-master branches Created: 04/Sep/19 Updated: 29/Oct/23 Resolved: 14/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Daly | Assignee: | Cristopher Stauffer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
Batch time should be increased. Exact time to be determined, but up to once a week. |
| Comments |
| Comment by Githook User [ 11/Sep/19 ] |
|
Author: {'name': 'Cristopher Stauffer', 'username': 'stauffec', 'email': 'cristopher.stauffer@mongodb.com'}Message: |
| Comment by Henrik Ingo (Inactive) [ 09/Sep/19 ] |
|
My proposal was to give up on the batchtime based scheduling completely, and instead add an Evergreen feature to schedule builds based on git tags. This would allow to schedule releases and release candidates automatically as Evergreen detects them. A related feature is then to automatically copy those results as baselines, removing the manual baselining work. In addition to those automatic builds, users could still manually schedule specific commits like a WT drop or to confirm an expected fix (or regression). |