[SERVER-80765] Reevaluate which tasks need to run on large instances Created: 05/Sep/23 Updated: 14/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Trevor Guidry | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Build
|
||||||||
| Participants: | |||||||||
| Description |
|
Some tasks were switched to large instances because they were running into build issues such as running out of memory on the default sizes. An example of this are ninja build variants on windows https://jira.mongodb.org/browse/SERVER-80752 After remote execution with bazel we should no longer need these large instances on some of these tasks and should revert back to the default sizes to save money. |