[performance] Regression in YAMLGeneration: 21.3% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkYAMLGeneration

Current Performance: 5,318,558 ns/op (5.32ms)
Historical Average: 4,384,626 ns/op (4.38ms)
Change: +21.3% slower

📈 Detailed Performance Metrics

Performance Comparison

• ns/op: 5,318,558 (was 4,384,626)
• Change: +21.3%
• Memory: 875,273 B/op
• Allocations: 7,453 allocs/op
• Historical Data Points: 9

Baseline Targets

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

💡 Recommended Actions

1. Review recent changes to YAML generation (pkg/workflow/compiler_yaml.go)
2. Run make bench-memory to generate memory profiles
3. Use go tool pprof to identify hotspots in the YAML generation step
4. Check for any new YAML marshaling or template expansions added recently
5. Compare with previous benchmark results using benchstat

📋 Additional Context

• Run ID: §24622185734
• Date: 2026-04-19
• Workflow: Daily CLI Performance

Generated by Daily CLI Performance Agent · ● 1.1M · ◷

• expires on Apr 21, 2026, 5:55 AM UTC

[github-actions]

🍪 *Issue Monster has assigned this to Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }

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! 🍪> [!CAUTION]

Security scanning requires review for Issue Monster

Details

Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

🍪 Om nom nom by Issue Monster · ● 21.9K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-04-21T05:55:25.385Z.

Closed by Workflow