Performance Impact Analyzer
When to Trigger
- •Database query changes
- •Adding loops or iterations
- •API route modifications
- •Large file operations
- •Keywords: "fetch", "query", "loop", "map", "filter"
What to Do
Step 1: Detect Anti-Patterns
Check for:
- •N+1 queries
- •Missing database indexes
- •Synchronous operations in loops
- •Large data fetches without pagination
- •Missing memoization (React)
- •Inefficient algorithms (O(n²) or worse)
Step 2: Estimate Impact
Report current vs after (e.g. query count, time). Explain why slower (e.g. N+1).
Step 3: Suggest Optimizations
- •Replace N+1 with single query using
include/selector JOINs. - •Add indexes for filtered/sorted columns.
- •Add pagination (skip/take or cursor).
- •Use
useMemo/useCallbackwhere appropriate. - •Prefer single aggregation over multiple sequential queries.
Show SLOW vs FAST code snippets. Ask: "Apply optimized version? (yes/no)".