[performance] Regression in CompileMemoryUsage: +81.9% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkCompileMemoryUsage
Current Performance: 13,431,229 ns/op (≈13.4ms)
Historical Average: 7,384,555 ns/op (≈7.4ms)
Change: +81.9% slower

📈 Detailed Performance Metrics

Performance Comparison

Metric	Current	Historical Avg	Change
ns/op	13,431,229	7,384,555	+81.9%
B/op	5,385,944	—	—
allocs/op	74,727	—	—

Historical Data Points: 7

Recent values (ns/op):

• 2026-03-16: 6,125,299
• 2026-03-17: 6,157,707
• 2026-03-18: 6,842,977
• 2026-03-19: 6,579,200
• 2026-03-20: 6,624,798
• 2026-03-21: 6,256,424
• 2026-03-22: 13,105,483 ← also elevated
• 2026-03-23: 13,431,229 ← today

Note: This regression appears to have started on 2026-03-22, doubling from baseline. The pattern is correlated with the CompileComplexWorkflow regression, suggesting a shared root cause.

💡 Recommended Actions

1. Investigate memory allocation patterns in the compiler — this benchmark specifically tracks memory usage
2. Run make bench-memory and check for memory profile changes since 2026-03-21
3. Review any changes to data structures or caching in pkg/workflow
4. Check if the correlated CompileComplexWorkflow regression shares the same root cause

📋 Additional Context

• Run ID: §23443107623
• Date: 2026-03-23
• Correlated regression: CompileComplexWorkflow (+82.9%)
• Benchmark: BenchmarkCompileMemoryUsage in pkg/workflow

References:

• §23443107623

Generated by Daily CLI Performance Agent · ◷

• expires on Mar 25, 2026, 2:48 PM 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 · ◷