Skill: Optimize Performance Profiling

Purpose

Prevent "premature optimization" and guesswork-based performance fixes. Enforce data-driven optimization using profiling tools to identify actual bottlenecks before making code changes.

1. Negative Knowledge (Anti-Patterns)

2. Verified Performance Procedure

The Profile-Optimize-Verify Cycle

1. BASELINE   → Measure current performance
2. PROFILE    → Identify actual bottlenecks
3. HYPOTHESIZE → Form theory about the cause
4. OPTIMIZE   → Apply targeted fix
5. MEASURE    → Verify improvement
6. REPEAT     → Continue until acceptable

Phase 1: Establish Baseline

Before optimizing, measure current performance:

# Frontend: Lighthouse audit
npx lighthouse https://localhost:3000 --view

# Backend: Load testing with autocannon
npx autocannon -c 100 -d 30 http://localhost:3000/api/users

# Bundle size analysis
npx vite-bundle-visualizer
# or for webpack:
npx webpack-bundle-analyzer dist/stats.json

Document baseline metrics:

Performance Baseline (2026-01-01)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Frontend:
  - First Contentful Paint: 1.2s
  - Time to Interactive: 3.5s
  - Total Bundle Size: 450 KB

Backend:
  - /api/users: avg 250ms, p95 800ms
  - /api/posts: avg 450ms, p95 1200ms
  - Throughput: 150 req/s

Database:
  - Slow queries (>1s): 3 queries
  - Connection pool usage: 80%

Phase 2: Profile to Find Bottlenecks

Frontend profiling:

// React DevTools Profiler
import { Profiler } from 'react';

function onRenderCallback(
  id: string,
  phase: 'mount' | 'update',
  actualDuration: number
) {
  console.log(`${id} (${phase}) took ${actualDuration}ms`);
}

<Profiler id="UserDashboard" onRender={onRenderCallback}>
  <UserDashboard />
</Profiler>

// Chrome DevTools Performance tab
// 1. Open DevTools → Performance
// 2. Click Record
// 3. Perform slow action
// 4. Stop recording
// 5. Analyze flame graph

Backend profiling (Node.js):

# CPU profiling
node --prof server.js
# Generate load, then:
node --prof-process isolate-*.log > profile.txt

# Memory profiling
node --inspect server.js
# Open chrome://inspect
# Take heap snapshot before and after operation

# Use clinic.js for comprehensive profiling
npx clinic doctor -- node server.js
# Generate load, then Ctrl+C
# Opens HTML report with flame graphs

Database profiling:

-- PostgreSQL: Enable slow query logging
ALTER DATABASE mydb SET log_min_duration_statement = 1000;

-- Find slow queries
SELECT query, mean_exec_time, calls
FROM pg_stat_statements
ORDER BY mean_exec_time DESC
LIMIT 10;

-- Explain query plan
EXPLAIN ANALYZE
SELECT * FROM users WHERE email = 'test@example.com';

3. Performance Benchmarking

Use the zero-context script:

# Benchmark a function
python .claude/skills/optimize-performance-profiling/scripts/benchmark.py \
  --file src/utils/sorting.ts \
  --function quickSort \
  --iterations 10000

# Compare before/after
python scripts/benchmark.py \
  --before src/utils/old.ts:slowFunction \
  --after src/utils/new.ts:fastFunction \
  --iterations 5000

Output example:

Benchmark Results
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Function: quickSort
Iterations: 10,000

Metrics:
  Average: 2.3ms
  Median:  2.1ms
  P95:     3.8ms
  P99:     5.2ms
  Min:     1.8ms
  Max:     12.1ms

Memory:
  Peak:    45.2 MB
  Average: 38.7 MB

4. Common Performance Fixes

For detailed code examples, see reference.md:

• N+1 Queries: Single query with JOIN, DataLoader batching
• Memory Leaks: Event listener cleanup, interval clearing
• Bundle Size: Tree-shaking, code splitting, dynamic imports
• Inefficient Algorithms: O(n) over O(n²), using Sets/Maps
• Database Indexing: CREATE INDEX on frequently queried columns
• Frontend Optimizations: Memoization, virtualization, lazy loading
• Backend Optimizations: Caching (LRU, Redis), connection pooling

Quick reference:

5. Performance Workflow for Agents

When asked to "make it faster" or "optimize":

1. Reject premature optimization

   User: "Optimize this function"
   Agent: "Let me first profile to identify if this is actually a bottleneck."
   

2. Establish baseline

   # Measure current performance
   npm run benchmark
   # Or lighthouse, autocannon, etc.
   

3. Profile to find bottlenecks

   # Use appropriate profiling tool
   node --prof server.js
   # or React DevTools Profiler
   

4. Identify the bottleneck

   • Is it CPU-bound? → Optimize algorithm
   • Is it I/O-bound? → Add caching, connection pooling
   • Is it network-bound? → Add compression, CDN
   • Is it database-bound? → Add indexes, optimize queries

5. Apply ONE optimization at a time

   • Fix the top bottleneck only
   • Don't optimize multiple things simultaneously

6. Measure improvement

   npm run benchmark
   # Compare before/after metrics
   

7. Verify no regressions

   npm test
   # Ensure functionality unchanged
   

8. Document improvement

   Performance improvement: /api/users endpoint
   Before: 450ms avg, 1200ms p95
   After:  120ms avg, 250ms p95
   Improvement: 73% faster (avg), 79% faster (p95)
   Method: Added database index on user_id column
   

Example Agent Session

User: "The dashboard is slow, make it faster"

Agent: "I'll profile the dashboard to identify bottlenecks."

[BASELINE]
Agent: Running Lighthouse audit...
Found: Time to Interactive = 5.2s, LCP = 3.8s

[PROFILE]
Agent: Opening React DevTools Profiler...
Found: UserTable component re-renders 47 times on page load
Found: Each render takes 180ms

[IDENTIFY]
Agent: Analyzing UserTable component...
Issue: Component re-renders on every parent state change
Issue: Not using virtualization for 5000 row table

[OPTIMIZE 1]
Agent: Wrapping UserTable in React.memo...
Testing... Re-renders reduced to 2

[MEASURE]
Agent: Running Lighthouse again...
Result: Time to Interactive = 3.1s (40% improvement)

[OPTIMIZE 2]
Agent: Implementing react-window virtualization...
Testing... Only rendering visible rows

[MEASURE]
Agent: Final Lighthouse audit...
Result: Time to Interactive = 1.8s (65% total improvement)
Verified: All tests still pass

Agent: "Dashboard optimized. TTI improved from 5.2s to 1.8s (65% faster)."

6. Failed Attempts (Negative Knowledge Evolution)

❌ Attempt: Micro-optimizations without profiling

Context: Replaced forEach with for loops for "performance" Failure: No measurable improvement, code less readable Learning: Profile first, optimize proven bottlenecks only

❌ Attempt: Added Redis cache everywhere

Context: Cached all database queries to "make it faster" Failure: Cache invalidation bugs, stale data, increased complexity Learning: Cache only hot paths identified by profiling

❌ Attempt: Memoized every React component

Context: Wrapped all components in React.memo Failure: No performance gain, harder to debug, memory overhead Learning: Memoize only components that re-render frequently

❌ Attempt: Aggressive code splitting

Context: Split every route into separate bundle Failure: Too many HTTP requests, worse performance Learning: Balance bundle size with HTTP request overhead

7. Performance Checklist

Before marking optimization as complete:

• Baseline Established: Current metrics documented
• Profiled: Used profiling tools to identify bottleneck
• Targeted Fix: Only optimized proven bottleneck
• Measured: Verified improvement with metrics
• Tests Pass: No functionality broken
• Documented: Performance improvement documented
• Acceptable: Performance now meets requirements

8. Extended Tools and Patterns

For comprehensive tool references and advanced patterns, see reference.md:

• Frontend Tools: Chrome DevTools, React DevTools, Lighthouse CI, Bundle Analyzers
• Backend Tools: Node.js profilers, clinic.js, autocannon, 0x
• Database Tools: EXPLAIN ANALYZE, pg_stat_statements, slow query logs
• Advanced Patterns: Web Workers, Request Coalescing, Progressive Enhancement
• Monitoring: Core Web Vitals, Custom Performance Marks
• Performance Budgets: CI integration, budget enforcement

9. Governance

• Token Budget: ~450 lines (within 500 limit)
• Extended Reference: See reference.md for detailed fixes, tools, and patterns
• Dependencies: Node.js profiling tools, Chrome DevTools, database-specific tools
• Pattern Origin: Performance Engineering best practices, Web Vitals
• Maintenance: Update as new profiling tools emerge
• Verification Date: 2026-01-01