[performance] Regression in ParseWorkflow: 10.8% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkParseWorkflow

Current Performance: 1,320,161 ns/op (1.32ms)
Historical Average: 1,190,085 ns/op (1.19ms)
Change: +10.8% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 1,320,161 (was ~1,190,085)
• B/op: 201,850
• allocs/op: 4,192
• Change: +10.8%
• Historical Data Points: 4

Baseline Targets

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

💡 Recommended Actions

1. Review recent changes to the parsing pipeline (pkg/parser/)
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots
4. Compare with previous benchmark results using benchstat
5. Check if any new validation rules or schema changes were added recently

📋 Additional Context

• Run ID: 24328112361
• Date: 2026-04-13
• Workflow: Daily CLI Performance
• Other benchmarks: 4 improvements, 2 stable — overall compilation performance is trending better
• Note: This regression is right at the threshold (+10.8% vs 10% threshold); monitor for the next few runs to determine if it's noise or a real regression

---

Automatically generated by Daily CLI Performance workflow

Generated by Daily CLI Performance Agent · ● 713.5K · ◷

• expires on Apr 15, 2026, 6:06 AM 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 · ● 171.9K · ◷