build-perf-diagnostics

To diagnose MSBuild performance bottlenecks, generate a binlog using dotnet build /bl, replay it to produce a performance summary, and review the results to pinpoint slow targets, tasks, and potential bottlenecks like low parallelism or excessive I/O.

ResolveAssemblyReferences can dominate MSBuild build time due to excessive reference resolution. By analyzing a binlog performance summary, you can identify if RAR is a bottleneck and apply targeted optimizations such as reducing references to improve build speed.

The best way to identify slow Roslyn analyzers is to generate a dotnet build binlog, replay it for a performance summary, and assess the analyzer timing sections to guide deferring expensive analyses and optimizing overall build performance.

To check MSBuild node utilization and parallelism, generate a binlog from your build, replay it to extract the performance summary, and review the node utilization data to identify serialization bottlenecks and guide improvements for build parallelism.

Yes, you can analyze both incremental and clean builds by generating a binlog for each scenario, replaying them to produce performance summaries, and reviewing the target and task performance sections to guide specific optimizations for each build type.