performance-gatelisted

# Gate 4: Performance Review > "Code that works is step one. Code that scales is step two." ## Purpose This gate catches performance anti-patterns before they cause problems. The focus is on obvious issues, not micro-optimizations. ## Gate Status - **PASS** — No obvious performance issues - **WARNING** — Issues found that could cause problems at scale --- ## Gate Questions ### Question 1: Scalability > "What happens when there are 10,000 items? 1,000,000?" **Looking for:** - Awareness of data growth - Pagination for large datasets - Efficient data structures - No unnecessary loops ### Question 2: Query Efficiency > "How many database queries does this operation make?" **Looking for:** - No N+1 queries - Bulk operations where appropriate - Indexes on queried columns - Awareness of query cost ### Question 3: Re-render Awareness (Frontend) > "When this state changes, what components re-render?" **Looking for:** - Awareness of render triggers - Appropriate memoization - State placement optimization - No expensive computations in render --- ## Performance Checklist ### Database Operations - [ ] No N+1 queries (queries inside loops) - [ ] Pagination for list endpoints - [ ] Indexes on frequently queried columns - [ ] SELECT only needed columns (not SELECT *) ### Frontend Rendering - [ ] Expensive computations use useMemo - [ ] Event handlers use useCallback where needed - [ ] Large lists use virtualization - [ ] Heavy components are lazy loaded ### API & Network -