[SERVER-80309] Design a mechanism to collect performance metrics Created: 22/Aug/23 Updated: 23/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Steve Gross | Assignee: | Daniel Moody |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Build
|
||||||||||||||||||||
| Sprint: | Build and Correctness OnDeck | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
We need to collect performance metrics for Bazel, including:
(daniel.moody updated info) One thing to note is that scons build metrics do not track remote icecream execution, because the metrics were originally designed for use in evergreen context (no icecream), and icecream does not have much in the way of metrics reporting options in any case. |
| Comments |
| Comment by Daniel Moody [ 17/Oct/23 ] |
|
There needs to be some clarification and categorization of scope and goals here. For example any kind of comparison of scons and bazel has to be done in a controlled way. Like you need to build the same thing in the same environment twice (one for scons and one for bazel) to compare. This comparison does not translate to developer use case. Sure we can track average developer build time, but there are so many underlying factors there that you don't what the root cause is for any given change. Also I believe there will be some overhead in build time while we have a "multi build system" build (similar to extra upfront cost for scons + ninja). There will be a cost for scons and bazel to communicate and work together, that will not be there if it was just scons or just bazel. |
| Comment by Alex Neben [ 22/Aug/23 ] |