[performance] Regression in CompileComplexWorkflow: +113.9% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkCompileComplexWorkflow

Current Performance: 13,943,459 ns/op (≈13.9ms)
Historical Average: 6,519,060 ns/op (≈6.5ms)
Change: +113.9% slower
Trend: Already elevated on 2026-03-21 (8,653,953 ns/op) — progressive degradation over 2 days

📈 Detailed Performance Metrics

Performance Comparison

Date	ns/op	Change
2026-03-15	5,975,399	baseline
2026-03-16	5,717,419	-4.3%
2026-03-17	6,358,182	+6.4%
2026-03-18	6,419,939	+7.4%
2026-03-19	6,312,211	+5.6%
2026-03-20	6,196,322	+3.7%
2026-03-21	8,653,953	+44.8% ⚠️
2026-03-22	13,943,459	+113.9% 🚨

• Memory: 5,821,560 B/op
• Allocations: 82,486 allocs/op
• Historical Data Points: 7
• 7-day Average: 6,519,060 ns/op

Baseline Targets

• Simple workflows: <100ms ✅
• Complex workflows: <500ms ✅ (still within target but degraded significantly)
• MCP-heavy workflows: <1s ✅

💡 Recommended Actions

1. Review recent commits touching complex workflow compilation (last 2 days)
2. Run make bench-memory to generate memory profiles for BenchmarkCompileComplexWorkflow
3. Use go tool pprof to identify hotspots in the complex workflow compilation path
4. Compare with benchstat against a known-good revision
5. Note: CompileMemoryUsage also regressed — changes may be related

📋 Additional Context

• Run ID: §23405229136
• Date: 2026-03-22
• Workflow: Daily CLI Performance
• Related regression: CompileMemoryUsage also shows +103.7% regression on the same run

References:

• §23405229136

Generated by Daily CLI Performance Agent · ◷

• expires on Mar 24, 2026, 2:41 PM 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 · ◷