[performance] Regression in CompileComplexWorkflow: 17.1% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkCompileComplexWorkflow

Current Performance: 9,564,329 ns/op (≈9.56ms)
Historical Average: 8,170,013 ns/op (≈8.17ms)
Change: +17.1% slower
Threshold: Regressions flagged at >10% change

📈 Detailed Performance Metrics

Performance Comparison

Metric	Value
Current ns/op	9,564,329 (~9.56ms)
Historical Average ns/op	8,170,013 (~8.17ms)
Change	+17.1%
Memory (B/op)	2,633,690
Allocations (allocs/op)	30,570
Historical Data Points	9

Baseline Targets

• Simple workflows: <100ms ✅ (well within)
• Complex workflows: <500ms ✅ (still within, but regressing)
• MCP-heavy workflows: <1s ✅ (well within)

Historical Trend (last 9 runs)

Date	ns/op
2026-03-15	5,975,399
2026-03-16	5,717,419
2026-03-17	6,358,182
2026-03-18	6,419,939
2026-03-19	6,312,211
2026-03-20	6,196,322
2026-03-21	8,653,953
2026-03-22	13,943,459
2026-03-23	9,306,029
2026-03-24	9,564,329 ⚠️

Note: The regression appears to have started around 2026-03-21 and has remained elevated.

💡 Recommended Actions

1. Review recent changes to the complex workflow compilation pipeline (around 2026-03-21)
2. Run make bench-memory to generate memory profiles for CompileComplexWorkflow
3. Use go tool pprof to identify performance hotspots in complex workflow handling
4. Compare with previous benchmark results using benchstat
5. Check if any new validation steps were added to the complex workflow path

📋 Additional Context

• Run ID: §23474858139
• Date: 2026-03-24
• Other Benchmarks: 5 improvements, 1 stable (only CompileComplexWorkflow regressed)
• Detection Method: Compared against 7-day rolling average of historical data

Notable: Most other benchmarks showed significant improvements today (CompileSimpleWorkflow: -70.4%, Validation: -60.8%, CompileMCPWorkflow: -44.6%), suggesting the complex workflow path may have a specific issue while general compilation improved.

References:

• §23474858139

Generated by Daily CLI Performance Agent · ◷

• expires on Mar 26, 2026, 5:43 AM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

The Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-03-26T05:43:23.355Z.

Closed by Workflow