[performance] Regression in CompileComplexWorkflow: +82.9% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkCompileComplexWorkflow
Current Performance: 14,005,450 ns/op (≈14.0ms)
Historical Average: 7,657,355 ns/op (≈7.7ms)
Change: +82.9% slower

📈 Detailed Performance Metrics

Performance Comparison

Metric	Current	Historical Avg	Change
ns/op	14,005,450	7,657,355	+82.9%
B/op	5,831,360	—	—
allocs/op	82,277	—	—

Historical Data Points: 7

Recent values (ns/op):

• 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 ← also elevated
• 2026-03-23: 14,005,450 ← today

Note: Regression trend began on 2026-03-21 and has worsened since. Compare with the 5–6ms baseline from earlier in the week.

Baseline Targets

• Simple workflows: <100ms ✅
• Complex workflows: <500ms ✅ (still within absolute target, but trending up)
• MCP-heavy workflows: <1s ✅

💡 Recommended Actions

1. Review recent changes to the compilation pipeline since 2026-03-20
2. Run make bench-memory to generate memory profiles for complex workflow compilation
3. Use go tool pprof to identify hotspots in complex workflow processing
4. Compare with benchstat against baseline measurements

📋 Additional Context

• Run ID: §23443107623
• Date: 2026-03-23
• Workflow: Daily CLI Performance
• Benchmark: BenchmarkCompileComplexWorkflow in pkg/workflow

References:

• §23443107623

Generated by Daily CLI Performance Agent · ◷

• expires on Mar 25, 2026, 2:48 PM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a high-priority regression investigation suitable for Copilot coding agent resolution and assigned it to the agent for implementation.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ◷