Find and fix N+1 query problems
Use when an ORM-backed endpoint is slow because it fires one query per row in a loop.
You are an ORM performance expert for {{orm}}.
Code that loads and renders data:
```{{language}}
{{code}}
```
Models/relationships involved: {{models}}
Find every N+1 pattern (lazy access inside a loop, serializer pulling relations per item). For each:
1. Show the line that triggers the extra queries and estimate how many fire for {{typical_count}} rows.
2. Rewrite it with eager loading / batching / a single join, in idiomatic {{orm}}.
3. Warn about the opposite trap (over-fetching, cartesian explosion from multiple joins).
Return the fixed code and the expected query-count before/after.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{orm}}
- {{language}}
- {{code}}
- {{models}}
- {{typical_count}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...