Perf Audit

Measure first, then explain, then ticket. No optimizing in this skill; query-optimizer and caching-strategy do the fixing.

Step 1: Scope

Get the specific slow thing: URL/endpoint, the user/role it's slow for, rough data size, and how slow ("4s on prod for org X"). Slow for one tenant and fast for others usually means data volume, so ask which tenant.

For a broad audit (no specific complaint), list the endpoints first and prioritize by traffic (ask, or check APM/access logs) × likely cost (list endpoints, nested serializers, reports, exports).

Step 2: Measure

Use what the project has, in this order:

1. APM (Sentry Performance, New Relic, Datadog, Scout) if the dev has access: the trace shows DB vs external vs Python time for real requests. Ask them to paste the trace summary.
2. A test that reproduces it with realistic volume. This is also the regression guard later: