Question - are there any tools that leverage the Detailed Build Summary to help identify the build bottlenecks?
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 141
Description
I have a solution with ~130 projects and according to the detailed build summary (obtained from the bin log) its node utilization is abysmal:
```
Utilization: 22.8 11.7 17.2 7.2 52.4 16.6 12.8 13.3 13.1 29.8 34.3 14.9 Average Utilization: 20.5104451261997
```
I would like to improve it. My plan is identify the bottleneck projects on which many other projects depend and check if there are transitive dependencies involving the bottleneck projects that can be short-circuited. For example, suppose A depends on B and B depends on C. Does A really need to depend on B? Maybe it can depend on C directly and the B dependency can be removed?
This kind of analysis requires tooling, so I wonder - do you guys have such tooling or anything that can help here? I am asking because I know you have created the detailed build summary to help you improve the performance, but I hardly believe you did all the leg work without automation.
Thank you,
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.