Optimization Review

Review Workflow

1. Map hotspots from changed code paths (UI rendering, API calls, DB access, event processing).
2. Estimate impact and frequency (hot path vs rare path).
3. Identify root causes (not just symptoms).
4. Propose minimal changes with expected impact, complexity, and risk.
5. Add verification guidance (benchmark, profile, regression checks).

Client Optimization Checklist

1. Rendering:
   • Unnecessary re-renders from unstable props/callbacks.
   • Missing memoization for expensive derived values.
2. State:
   • Over-broad global state or duplicated state.
   • Misuse of client state for server state.
3. Data Fetching:
   • Missing TanStack Query caching/invalidation strategy.
   • Duplicate requests and unbounded refetching.
4. App Router:
   • Incorrect client/server split causing extra JS payload.
5. Bundle/UI:
   • Large client bundles, missing code-splitting/lazy loading.
   • Expensive list rendering without virtualization/pagination where needed.

Server Optimization Checklist

1. Data Layer:
   • N+1 query risks, over-fetching, missing pagination.
   • Missing indexes for high-volume access patterns.
2. Service Layer:
   • Blocking operations on hot paths.
   • Repeated expensive transformations/serialization.
3. External Calls:
   • Missing context timeouts/circuit-breaker/retry strategy.
4. Events:
   • Inefficient outbox polling/dispatch loops.
   • Duplicate event handling risks and missing idempotency checks.
5. Caching:
   • Candidate read paths for Redis or in-memory caching.
   • Incorrect TTL/invalidation assumptions.

Required Output Format

1. Bottleneck summary (top issues first).
2. Findings by severity and impact: Critical, High, Medium, Low.
3. For each finding provide:
   • Title
   • File and line reference
   • Root cause
   • Performance impact (latency/throughput/resource cost)
   • Minimal optimization recommendation
   • Risk level and rollback note
   • Verification method (profile/benchmark/test)
4. Prioritized optimization plan (quick wins first).
5. Residual risks and measurement gaps.

If No Findings

1. Explicitly state no significant optimization issues found.
2. Provide monitoring recommendations for future regressions.