Django Query Profiling
Use this skill to turn a vague slow-Django report into a specific queryset, SQL statement, and reproducible scenario.
Workflow
Start from the user-visible slow path.
- Record the URL, API action, background task, management command, or report.
- Capture request parameters, user or tenant shape, pagination state, and data volume.
Collect production or staging evidence.
- Prefer APM transaction traces when available.
- Use database slow-query logs for SQL that is slow independent of Python.
- Use Django Debug Toolbar for server-rendered pages in local development.
- For APIs or jobs, add targeted query logging around the suspicious block.
Map SQL back to Django code.
- Search model table names and column names.
- Inspect view
get_queryset(), serializer fields, template loops, managers, model properties, and signal handlers.
- Check whether related-object access happens after the initial queryset was evaluated.
Reproduce locally or in a safe shell.
- Use production-like row counts when possible.
- Disable unrelated instrumentation and debug-only middleware when measuring.
- Keep a repeatable script, test, or shell snippet that exercises the slow path.
Route the fix.
- Query count issue: use
django-orm-query-optimization.
- One slow SQL statement: use
django-query-plan-reading.
- Large loops or writes: use
django-queryset-batch-processing.
See tooling-and-reproduction.md for concrete profiling snippets and pitfalls.
Good Evidence
- Query count before/after for the specific path.
- The slow SQL or normalized SQL fingerprint.
- Stack or code pointer that explains where the SQL originates.
- Timing from the same environment and representative data shape.
Verification
Do not finish profiling with only a hunch. Finish with a named queryset, code path, and command or request that another agent can re-run.
1---2name: django-query-profiling3description: Find the Django ORM code and request path responsible for slow SQL by using APM traces, slow query logs, Django Debug Toolbar, query logging, and local reproduction. Use when a Django database performance issue is suspected but the exact queryset, view, serializer, template, or job causing it is not yet proven.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 source: https://skillmd.com/skills/hashgraph-online/django-query-profiling8 version: "0.1.0"9 displayName: Django Query Profiling10 category: Django11 tags: django,database,profiling,apm,debug-toolbar12---1314# Django Query Profiling1516Use this skill to turn a vague slow-Django report into a specific queryset, SQL statement, and reproducible scenario.1718## Workflow19201. Start from the user-visible slow path.21 - Record the URL, API action, background task, management command, or report.22 - Capture request parameters, user or tenant shape, pagination state, and data volume.23242. Collect production or staging evidence.25 - Prefer APM transaction traces when available.26 - Use database slow-query logs for SQL that is slow independent of Python.27 - Use Django Debug Toolbar for server-rendered pages in local development.28 - For APIs or jobs, add targeted query logging around the suspicious block.29303. Map SQL back to Django code.31 - Search model table names and column names.32 - Inspect view `get_queryset()`, serializer fields, template loops, managers, model properties, and signal handlers.33 - Check whether related-object access happens after the initial queryset was evaluated.34354. Reproduce locally or in a safe shell.36 - Use production-like row counts when possible.37 - Disable unrelated instrumentation and debug-only middleware when measuring.38 - Keep a repeatable script, test, or shell snippet that exercises the slow path.39405. Route the fix.41 - Query count issue: use `django-orm-query-optimization`.42 - One slow SQL statement: use `django-query-plan-reading`.43 - Large loops or writes: use `django-queryset-batch-processing`.4445See [tooling-and-reproduction.md](references/tooling-and-reproduction.md) for concrete profiling snippets and pitfalls.4647## Good Evidence4849- Query count before/after for the specific path.50- The slow SQL or normalized SQL fingerprint.51- Stack or code pointer that explains where the SQL originates.52- Timing from the same environment and representative data shape.5354## Verification5556Do not finish profiling with only a hunch. Finish with a named queryset, code path, and command or request that another agent can re-run.