[performance] Regression in CompileComplexWorkflow: +18.9% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkCompileComplexWorkflow

Current Performance: 11,641,260 ns/op (11.64ms)
Historical Average: 9,786,416 ns/op (9.79ms)
Change: +18.9% slower

📈 Detailed Performance Metrics

Performance Comparison

Metric	Current	Historical Avg	Change
ns/op	11,641,260	9,786,416	+18.9%
B/op	2,757,181	—	—
allocs/op	30,865	—	—

Historical Data Points

• Data points used: 7 runs
• Trend: Consistent regression vs recent average

Baseline Targets

• Simple workflows: <100ms ✅ (currently 11.64ms)
• Complex workflows: <500ms ✅ (currently 11.64ms, but trending up)
• MCP-heavy workflows: <1s ✅

💡 Recommended Actions

1. Review recent changes to the compilation pipeline
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots in complex workflow compilation
4. Compare with previous benchmark results using benchstat
5. Check for added validation steps or new schema processing that may apply only to complex workflows

📋 Additional Context

• Run ID: 24438690812
• Date: 2026-04-15
• Workflow: Daily CLI Performance
• Note: Improvements detected in other benchmarks (Validation -37.6%, ParseWorkflow -11.8%) suggesting changes were made recently that may have unintentionally added overhead to complex workflow compilation

References: §24438690812

Generated by Daily CLI Performance Agent · ● 764.7K · ◷

• expires on Apr 17, 2026, 5:55 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 · ● 170.4K · ◷