How can performance bottlenecks in Bamboo CI/CD pipelines be identified?

Determining why a Bamboo build exceeds expected duration requires understanding which part of the pipeline consumes the most time and whether external factors such as agent load or network latency are involved. The goal is to isolate the responsible stage—compilation, testing, or deployment—while accounting for variability in agent hardware and repository access. It is also uncertain whether a single baseline duration is sufficient or if separate baselines should be maintained for different agent pools.

Which metrics provide the clearest view of individual stage execution times? How can agent CPU and memory utilization be effectively correlated with overall build length? What specific network latency measurements (e.g., time to fetch dependencies or push artifacts) are most indicative of a bottleneck? Should baseline performance be calculated per agent pool or across the entire fleet? What logging granularity is needed to capture stage start and end timestamps reliably?