[SERVER-85960] Review EngFlow Utilization after Phase 1 Completion Created: 30/Jan/24  Updated: 01/Feb/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Zack Winter Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Build
Participants:

 Description   

After phase 1 we will have bazel enabled on all variants compiling a small number (few hundred) source files per build. Monitor EngFlow utilization metrics to create a rough estimate of when we'll run out of the 400 cores EngFlow has currently allocated to us.

The lag time between capacity requests is about a month, so we should ask for what we'll need for the next two months.

1. Monitor the peak core utilization of our engflow cluster with the current number of source files building
2. Figure out an appropriate multiplier that we'll need for the next couple months. This should be (total number of source files in 10gen/mongo) / (current number of source files building with bazel)
3. Multiply #1 and #2 to get a capacity estimate, request about 1.5-2x that to be safe


Generated at Thu Feb 08 06:59:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.