How can Bazel build performance be diagnosed using measurements and profiling while minimizing measurement overhead?
Diagnosing Bazel build performance involves collecting timing and resource usage data to pinpoint actions that dominate the overall build latency, while ensuring that the profiling mechanism itself does not significantly distort the results. Because builds may involve remote execution, caching, and incremental changes, the collected metrics must be interpret