[performance] Regression in CompileMCPWorkflow: +31.0% slower

[github-actions]

Benchmark: CompileMCPWorkflow

Current Performance: 548,691 ns/op (548.69μs)
Historical Average: 418,950 ns/op (418.95μs)
Change: +31.0% slower

📈 Detailed Performance Metrics

• ns/op: 548,691 (was 418,950)
• B/op: 136,317
• allocs/op: 2,371
• Change: +31.0%
• Historical Data Points: 3

Baseline Targets

• Simple workflows: <100ms
• Complex workflows: <500ms
• MCP-heavy workflows: <1s

Note: CompileMCPWorkflow (548μs) is well within the 1s target, but exceeded the 10% regression threshold compared to the 2-day historical average (418μs). May reflect CI variance; monitoring recommended.

💡 Recommended Actions

1. Review recent changes to the MCP workflow compilation path
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots
4. Compare with previous results using benchstat

📋 Additional Context

• Run ID: 28248123524
• Date: 2026-06-26
• Workflow: Daily CLI Performance

---

Automatically generated by Daily CLI Performance workflow

Generated by ⚡ Daily CLI Performance Agent · 53.3 AIC · ⌖ 20 AIC · ⊞ 11.3K · ◷

• expires on Jun 28, 2026, 7:42 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 · 4.22 AIC · ⌖ 23.9 AIC · ⊞ 5.6K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-06-28T15:42:26.275Z.

Closed by Workflow