[performance] Regression in CompileSimpleWorkflow: +157.3% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: CompileSimpleWorkflow

Current Performance: 14,602,609 ns/op (14.60ms)
Historical Average: 5,675,000 ns/op (5.67ms)
Change: +157.3% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 14,602,609 (was ~5,675,000)
• Change: +157.3%
• Memory: 6,099,802 B/op (was ~1,215,781 B/op)
• Allocations: 73,636 allocs/op (was ~6,251 allocs/op)
• Historical Data Points: 14

Baseline Targets

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

💡 Recommended Actions

1. Review recent changes to the workflow compilation pipeline (especially since 2026-04-03)
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots
4. Note: memory and alloc counts increased dramatically (~12x), suggesting structural changes
5. Compare with previous benchmark results using benchstat

📋 Additional Context

• Run ID: 28955095507
• Date: 2026-07-08
• Workflow: Daily CLI Performance
• Note: Concurrent regressions also detected in CompileComplexWorkflow (+94.9%), CompileMemoryUsage (+124.0%), and YAMLGeneration (+143.6%).

---

Automatically generated by Daily CLI Performance workflow

Generated by ⚡ Daily CLI Performance Agent · 97.4 AIC · ⌖ 14.5 AIC · ⊞ 11.4K · ◷

• expires on Jul 10, 2026, 7:49 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

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

If assignment succeeds, 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 · 1.16 AIC · ⌖ 4.78 AIC · ⊞ 5.5K · ◷