[performance] Regression in YAMLGeneration: +143.6% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: YAMLGeneration

Current Performance: 12,359,010 ns/op (12.36ms)
Historical Average: 5,073,000 ns/op (5.07ms)
Change: +143.6% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 12,359,010 (was ~5,073,000)
• Change: +143.6%
• Memory: 6,011,258 B/op (was ~1,198,197 B/op)
• Allocations: 72,156 allocs/op (was ~5,711 allocs/op)
• Historical Data Points: 14

Baseline Targets

• YAML generation is a sub-phase of workflow compilation

💡 Recommended Actions

1. Review recent changes to YAML generation logic
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots in the YAML generation phase
4. Note: memory and alloc counts increased ~5x, suggesting significant structural changes
5. Compare with previous benchmark results using benchstat

📋 Additional Context

• Run ID: 28955095507
• Date: 2026-07-08
• Workflow: Daily CLI Performance
• Note: Part of a broader compilation regression pattern; CompileSimpleWorkflow (+157.3%), CompileMemoryUsage (+124.0%), and CompileComplexWorkflow (+94.9%) also regressed.

---

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.2 AIC · ⌖ 8.27 AIC · ⊞ 8.1K · ◷