Evaluates and compares performance characteristics of technologies including speed, resource usage, and scalability.
Analyzes and compares performance metrics like speed, resource usage, and scalability across technologies. Use it to evaluate benchmarks and identify performance trade-offs for your stack.
/plugin marketplace add avovello/cc-plugins/plugin install research@cc-pluginsEvaluates and compares performance characteristics of technologies including speed, resource usage, and scalability.
✅ DOES:
❌ DOES NOT:
## Bundle Size Comparison
| Library | Minified | Gzipped | % of 100KB Budget |
|---------|----------|---------|-------------------|
| Redux + React-Redux + RTK | 52 KB | 18.5 KB | 18.5% |
| Zustand | 3.2 KB | 1.1 KB | 1.1% |
| MobX + mobx-react-lite | 45 KB | 16 KB | 16% |
**Winner**: Zustand (94% smaller than Redux)
**Impact**:
- Initial page load time
- Mobile users on slow connections
- Total JavaScript execution time
## Benchmark Results
### State Update Performance (10,000 updates/sec)
| Library | Updates/sec | Memory Usage | CPU Usage |
|---------|-------------|--------------|-----------|
| Redux | 8,500 | 12 MB | 45% |
| Zustand | 9,200 | 8 MB | 40% |
| MobX | 9,800 | 10 MB | 38% |
**Winner**: MobX (15% faster than Redux)
### Component Re-render Optimization
| Library | Unnecessary Re-renders | Optimization Method |
|---------|------------------------|---------------------|
| Redux | 5-10% | Manual with selectors |
| Zustand | 3-5% | Automatic with shallow compare |
| MobX | 0-2% | Automatic with observables |
**Winner**: MobX (best automatic optimization)
## Scalability Assessment
### Large Application Performance
**Test**: 100 components, 10,000 state updates
| Library | Initial Render | Update Time | Memory Growth |
|---------|----------------|-------------|---------------|
| Redux | 45ms | 2.5ms | Stable |
| Zustand | 38ms | 2.1ms | Stable |
| MobX | 42ms | 1.8ms | Stable |
### Scaling Characteristics
**Redux**:
- ✅ Predictable performance at any scale
- ✅ No performance degradation with size
- ⚠️ Selector optimization required
**Zustand**:
- ✅ Excellent performance
- ✅ Minimal overhead
- ✅ Scales well naturally
**MobX**:
- ✅ Excellent performance with observables
- ⚠️ Can slow down with too many observers
- ⚠️ Need to manage observable scope
# Performance Evaluation Report
## Summary
| Metric | Redux | Zustand | MobX | Winner |
|--------|-------|---------|------|--------|
| Bundle Size | 18.5 KB | 1.1 KB | 16 KB | Zustand |
| Update Speed | 8,500/s | 9,200/s | 9,800/s | MobX |
| Memory Usage | 12 MB | 8 MB | 10 MB | Zustand |
| Re-render Optimization | Manual | Auto | Auto | MobX |
| **Overall** | **Good** | **Excellent** | **Excellent** | **Zustand/MobX** |
## Detailed Analysis
[Full benchmark data and analysis]
## Performance Recommendations
- **Small apps**: Zustand (minimal overhead)
- **Large apps with complex state**: Redux (predictable)
- **Apps needing reactive programming**: MobX (automatic optimization)
## Trade-offs
**Redux**:
- Slightly larger bundle
- Manual optimization needed
- But very predictable
**Zustand**:
- Tiny bundle
- Great performance
- Limited tooling impact
**MobX**:
- Automatic optimization
- Best re-render performance
- But less predictable
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>