Profiling Software Performance

Use this skill to make performance work empirical. The goal is to identify the constraint that matters, change only what the evidence supports, and prove the result against a comparable baseline.

Required Inputs

• A target workload or user-visible operation.
• A measurable objective, such as latency percentile, throughput, memory, allocation rate, startup time, build time, or CPU time.
• The command, scenario, fixture, request, trace, benchmark, or reproduction path that exercises the workload.
• Relevant constraints: hardware, environment, data size, concurrency, external services, caching state, and acceptable tradeoffs.

If the user gives only a vague symptom, first turn it into a measurable workload and say what will be measured.

Workflow