3.6 KiB
3.6 KiB
description, model
| description | model |
|---|---|
| Analyze and optimize code for performance, memory, and efficiency | claude-sonnet-4-5 |
Optimize the following code for performance and efficiency.
Code to Optimize
$ARGUMENTS
Optimization Strategy for Solo Developers
1. Profiling First
- Identify actual bottlenecks
- Don't optimize prematurely
- Measure before and after
- Focus on high-impact areas
2. Performance Optimization Areas
React/Next.js
- Memoization (React.memo, useMemo, useCallback)
- Code splitting and lazy loading
- Image optimization (next/image)
- Font optimization (next/font)
- Remove unnecessary re-renders
- Virtual scrolling for long lists
Database Queries
- Add indexes for frequently queried fields
- Batch queries (reduce N+1 problems)
- Use select to limit fields
- Implement pagination
- Cache frequent queries
- Use database views for complex joins
API Calls
- Implement caching (SWR, React Query)
- Debounce/throttle requests
- Parallel requests where possible
- Request deduplication
- Optimistic updates
Bundle Size
- Tree-shaking unused code
- Dynamic imports for large libraries
- Replace heavy dependencies
- Code splitting by route
- Lazy load below-the-fold content
Memory
- Fix memory leaks (cleanup useEffect)
- Avoid unnecessary object creation
- Use const for non-changing values
- Clear intervals/timeouts
- Remove event listeners
3. Optimization Checklist
JavaScript/TypeScript
- Use const/let instead of var
- Avoid nested loops where possible
- Use Map/Set for lookups
- Minimize DOM manipulations
- Debounce/throttle expensive operations
React
- Memo components that render often
- Move static values outside components
- Use keys properly in lists
- Avoid inline functions in render
- Lazy load routes and components
Next.js
- Use Server Components where possible
- Implement ISR for dynamic content
- Optimize images with next/image
- Prefetch critical routes
- Use Suspense for streaming
Database
- Add indexes on foreign keys
- Use prepared statements
- Batch inserts/updates
- Implement connection pooling
- Cache expensive queries
Network
- Compress responses (gzip/brotli)
- Use CDN for static assets
- Implement HTTP/2
- Set proper cache headers
- Minimize payload size
4. Measurement Tools
Frontend
- Chrome DevTools Performance tab
- Lighthouse CI
- React DevTools Profiler
- Bundle Analyzer (next/bundle-analyzer)
Backend
- Node.js profiler
- Database query analyzer
- APM tools (DataDog, New Relic)
- Load testing (k6, Artillery)
5. Common Optimizations
Replace inefficient array methods
// Before: Multiple iterations
const result = arr
.filter(x => x > 0)
.map(x => x * 2)
.reduce((sum, x) => sum + x, 0)
// After: Single iteration
const result = arr.reduce((sum, x) => {
return x > 0 ? sum + (x * 2) : sum
}, 0)
Memoize expensive calculations
const expensiveValue = useMemo(() => {
return complexCalculation(props.data)
}, [props.data])
Virtual scrolling for long lists
import { useVirtual } from 'react-virtual'
// Only render visible items
Output Format
- Analysis - Identify performance bottlenecks
- Optimized Code - Improved version
- Explanation - What changed and why
- Benchmarks - Expected performance improvement
- Trade-offs - Any complexity added
- Next Steps - Further optimization opportunities
Focus on practical, measurable optimizations that provide real user value. Don't sacrifice readability for micro-optimizations.