Skip to content

ALL-PERF1001 · profiling_evidence

Judge whether a performance decision has adequate profiling evidence.

This is a contextual rule for all languages. Read its implementation.

Check workload, environment, baseline, profiler, measured resource, bottleneck, and recency before accepting performance evidence.

Findings cite profiles, commands, hardware, workloads, baselines, and timestamps.

Removing obviously dead work can be justified without a full profile when behavior is proven.

A saved profile over the production workload is sufficient. A microbenchmark from an old implementation is stale for a current system claim.

  • Cites “Systems Performance”
  • Cites “The Python Standard Library”, profiling