[performance] Regression in CompileMemoryUsage: +124.0% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: CompileMemoryUsage

Current Performance: 17,426,973 ns/op (17.43ms)
Historical Average: 7,780,000 ns/op (7.78ms)
Change: +124.0% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 17,426,973 (was ~7,780,000)
• Change: +124.0%
• Memory: 8,317,594 B/op (was ~1,714,125 B/op)
• Allocations: 94,378 allocs/op (was ~9,441 allocs/op)
• Historical Data Points: 14

Baseline Targets

• Complex workflows: <500ms ✅ (still within target)

💡 Recommended Actions

1. Review recent changes to memory handling in workflow compilation
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof -alloc_objects to identify allocation hotspots
4. Note: allocation count increased ~10x (9,441 → 94,378 allocs/op), indicating major 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 alongside CompileSimpleWorkflow (+157.3%), YAMLGeneration (+143.6%), and CompileComplexWorkflow (+94.9%).

---

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.24 AIC · ⌖ 5.93 AIC · ⊞ 8K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-07-10T15:49:12.033Z.

Closed by Workflow