build-perf-baseline

To establish a build performance baseline, run cold, warm, and no-op dotnet builds with structured binary logs to measure starting performance. This verifies restore and compile behavior while confirming incremental build health before applying any optimizations.

The best way to optimize slow dotnet build times is to measure baselines first using binary logs, then apply targeted levers like MSBuild Server, deterministic outputs, static graph builds, and parallelism tuning to reduce critical path rebuilds.

MSBuild Server and static graph builds are targeted optimization levers that improve .NET incremental builds by tuning parallelism and dependency graph trimming. Measuring cold, warm, and no-op scenarios with binary logs proves their impact on critical path rebuilds.

Diagnose regressing build times in large multi-project solutions by capturing baseline measurements across no-op and warm builds with binary logs. This quantifies where build time is spent to prove the impact of CI configuration changes.

Configure UseArtifactsOutput and reference trimming when baseline measurements show unhealthy incremental behavior or slow warm builds. These MSBuild levers reduce critical path rebuilds and improve deterministic outputs after establishing initial binary log baselines.