📊 Performance Regression Detected
Benchmark: CompileMCPWorkflow
Current Performance: 437,466 ns/op (437.47μs)
Historical Average: 382,050 ns/op (382.05μs)
Change: +14.5% slower
📈 Detailed Performance Metrics
Performance Comparison
- ns/op: 437,466 (was 382,050)
- Change: +14.5%
- Memory: 147,736 B/op, 2,919 allocs/op
- Historical Data Points: 2
Baseline Targets
- Simple workflows: <100ms
- Complex workflows: <500ms
- MCP-heavy workflows: <1s (current: 437.47μs ✅ within target, but regressing)
📊 Context
While CompileMCPWorkflow remains within its <1s target (437μs), it has regressed 14.5% compared to the historical average. Most other benchmarks improved significantly (20-40% faster) this run, making this regression stand out.
ParseWorkflow also shows a +6.9% warning trend and may need monitoring.
💡 Recommended Actions
- Review recent changes to the MCP workflow compilation path
- Run
make bench-memory to generate memory profiles for MCP workflows
- Use
go tool pprof to identify hotspots in MCP compilation
- Compare with previous benchmark results using
benchstat
- Monitor
ParseWorkflow (+6.9%) in upcoming runs
📋 Full Run Context
| Benchmark |
Current |
Historical Avg |
Change |
| CompileSimpleWorkflow |
2.30ms |
3.20ms |
-28.0% ✨ |
| CompileComplexWorkflow |
3.30ms |
4.39ms |
-24.9% ✨ |
| CompileMCPWorkflow |
437.47μs |
382.05μs |
+14.5% ⚠️ |
| CompileMemoryUsage |
2.83ms |
3.97ms |
-28.8% ✨ |
| ParseWorkflow |
301.40μs |
282.00μs |
+6.9% ⚡ |
| Validation |
25.52μs |
31.85μs |
-19.8% ✨ |
| YAMLGeneration |
2.25ms |
3.80ms |
-40.9% ✨ |
| ExtractWorkflowNameFromFile |
7.11μs |
7.21μs |
-1.4% ✓ |
| FindIncludesInContent |
180ns |
173ns |
+4.0% ✓ |
Automatically generated by Daily CLI Performance workflow
Generated by ⚡ Daily CLI Performance Agent · 54.9 AIC · ⌖ 14.2 AIC · ⊞ 11.4K · ◷
📊 Performance Regression Detected
Benchmark: CompileMCPWorkflow
Current Performance: 437,466 ns/op (437.47μs)
Historical Average: 382,050 ns/op (382.05μs)
Change: +14.5% slower
📈 Detailed Performance Metrics
Performance Comparison
Baseline Targets
📊 Context
While
CompileMCPWorkflowremains within its <1s target (437μs), it has regressed 14.5% compared to the historical average. Most other benchmarks improved significantly (20-40% faster) this run, making this regression stand out.ParseWorkflowalso shows a +6.9% warning trend and may need monitoring.💡 Recommended Actions
make bench-memoryto generate memory profiles for MCP workflowsgo tool pprofto identify hotspots in MCP compilationbenchstatParseWorkflow(+6.9%) in upcoming runs📋 Full Run Context
Automatically generated by Daily CLI Performance workflow