📊 Performance Regression Detected
BenchmarkCompileMCPWorkflow is 20.1% slower than the recent historical average (last 7 runs).
Key Metrics
| Metric |
Value |
| Current |
9,769,572 ns/op (~9.8ms) |
| Historical Average (7-run) |
~8,136,617 ns/op (~8.1ms) |
| Change |
+20.1% slower |
| Historical Data Points |
13 |
📈 Historical Trend for CompileMCPWorkflow
| Date |
ns/op |
| 2026-03-22 |
8,146,212 |
| 2026-03-23 |
6,808,130 |
| 2026-03-24 |
7,831,997 |
| 2026-03-31 |
5,668,083 |
| 2026-04-01 |
6,157,630 |
| 2026-04-02 |
4,942,122 |
| 2026-04-03 (current) |
9,769,572 ⚠️ |
Note: Values prior to 2026-03-22 were 15–17ms range; a significant optimization dropped them to ~5–8ms. Today's value represents a partial regression relative to that improved baseline.
📋 Full Benchmark Context (2026-04-03)
| Benchmark |
ns/op |
Change |
| CompileSimpleWorkflow |
6,578,959 |
✨ −39.6% |
| CompileComplexWorkflow |
9,456,182 |
✓ −0.8% |
| CompileMCPWorkflow |
9,769,572 |
⚠️ +20.1% |
| CompileMemoryUsage |
7,860,516 |
✨ −9.6% |
| ParseWorkflow |
976,922 |
✨ −45.4% |
| Validation |
1,769,602 |
✨ −35.3% |
| YAMLGeneration |
4,509,263 |
✨ −28.9% |
| ExtractWorkflowNameFromFile |
11,371 |
✨ −28.1% |
| FindIncludesInContent |
26,098 |
✨ −24.2% |
💡 Recommended Actions
- Review recent changes to MCP workflow compilation (toolset handling, MCP server config parsing)
- Run
make bench-memory to generate memory profiles for MCP compilation
- Use
go tool pprof to identify hotspots in MCP-specific code paths
- Compare with previous results using
benchstat
- Re-run benchmarks to confirm (benchmark variance is expected on CI runners)
⚠️ Note on Significance
The performance baseline was established after March 22. This run's value (9.8ms) is notably higher than the recent 4.9–8.1ms range. Verify whether this is a real regression or runner variance by checking subsequent daily runs.
References:
Generated by Daily CLI Performance Agent · ● 805.1K · ◷
📊 Performance Regression Detected
BenchmarkCompileMCPWorkflowis 20.1% slower than the recent historical average (last 7 runs).Key Metrics
📈 Historical Trend for CompileMCPWorkflow
Note: Values prior to 2026-03-22 were 15–17ms range; a significant optimization dropped them to ~5–8ms. Today's value represents a partial regression relative to that improved baseline.
📋 Full Benchmark Context (2026-04-03)
💡 Recommended Actions
make bench-memoryto generate memory profiles for MCP compilationgo tool pprofto identify hotspots in MCP-specific code pathsbenchstatThe performance baseline was established after March 22. This run's value (9.8ms) is notably higher than the recent 4.9–8.1ms range. Verify whether this is a real regression or runner variance by checking subsequent daily runs.
References: