[performance] Regression in CompileComplexWorkflow: 16.5% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: CompileComplexWorkflow

Current Performance: 11,710,787 ns/op (11.71ms)
Historical Average: 10,055,622 ns/op (10.06ms)
Change: +16.5% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 11,710,787 (was 10,055,622)
• Change: +16.5%
• B/op: 3,008,568
• allocs/op: 32,802
• Historical Data Points: 2

Baseline Targets

• Simple workflows: <100ms ✅ (5.74ms)
• Complex workflows: <500ms ✅ (11.71ms — within budget, but trending up)
• MCP-heavy workflows: <1s ✅

💡 Recommended Actions

1. Review recent changes to the compilation pipeline for complex workflows
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots in CompileComplexWorkflow
4. Compare with previous benchmark results using benchstat

📋 Additional Context

• Run ID: §24066354673
• Date: 2026-04-07
• Other regressions: YAMLGeneration (+18.9%), Validation (+20.1%)
• Improvements in same run: CompileSimpleWorkflow (-9.0%), CompileMCPWorkflow (-8.7%), ParseWorkflow (-22.2%)

Note: With only 2 historical data points, this comparison has limited statistical confidence. Continue monitoring across future runs.

Generated by Daily CLI Performance Agent · ● 1.4M · ◷

• expires on Apr 9, 2026, 5:51 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 · ● 640.9K · ◷