Performance Regression

Establish whether the reported workload regressed, which operation multiplied, and whether the benchmark can distinguish the known-good and known-bad builds. Preserve the user's requested scope: an investigation does not authorize production fixes, publishing reports, or cloud operations.

Evidence and workload selection

Search docs/fixes for the affected command, subsystem, and symptoms. Use the relevant fix logs as the source for incident history, reproduction conditions, and known-good/bad revisions; verify those details against the implementation and current behavior.

Record the command, flags, scale, configuration shape, and external operations that trigger the slowdown. Reproduce the reported command itself: a faster neighboring command does not establish that the affected path improved.