📊 Performance Regression Detected
Benchmark: BenchmarkParseWorkflow
Current Performance: 1,387,952 ns/op (1.39ms)
Historical Average: 847,890 ns/op (847.89μs)
Change: +63.7% slower
📈 Detailed Performance Metrics
Performance Comparison
- ns/op: 1,387,952 (was 847,890)
- Change: +63.7%
- Memory: 158,625 B/op
- Allocations: 2,870 allocs/op
- Historical Data Points: 9
Baseline Targets
- Simple workflows: <100ms
- Complex workflows: <500ms
- MCP-heavy workflows: <1s
💡 Recommended Actions
- Review recent changes to the workflow parsing phase (
pkg/workflow/parser or pkg/parser)
- Run
make bench-memory to generate memory profiles
- Use
go tool pprof to identify hotspots in the parse step
- Compare with previous benchmark results using
benchstat
📋 Additional Context
Generated by Daily CLI Performance Agent · ● 1.1M · ◷
📊 Performance Regression Detected
Benchmark:
BenchmarkParseWorkflowCurrent Performance: 1,387,952 ns/op (1.39ms)
Historical Average: 847,890 ns/op (847.89μs)
Change: +63.7% slower
📈 Detailed Performance Metrics
Performance Comparison
Baseline Targets
💡 Recommended Actions
pkg/workflow/parserorpkg/parser)make bench-memoryto generate memory profilesgo tool pprofto identify hotspots in the parse stepbenchstat📋 Additional Context