📊 Performance Regression Detected
Benchmark: YAMLGeneration
Current Performance: 9,663,952 ns/op (9.66ms)
Historical Average: 3,647,443 ns/op (3.65ms)
Change: +164.9% slower
📈 Detailed Performance Metrics
Performance Comparison
- ns/op: 9,663,952 (was 3,647,443)
- Change: +164.9%
- Bytes/op: 6,027,672 B/op (was ~850,520 B/op)
- Allocs/op: 66,976 allocs/op (was ~5,435 allocs/op)
- Historical Data Points: 5
Baseline Targets
- YAML generation is a sub-phase of complex workflows (<500ms) ✅
💡 Recommended Actions
- Review recent changes to the YAML generation pipeline (regression began ~June 11)
- Run
make bench-memory to generate memory profiles
- Use
go tool pprof to identify hotspots — memory regressed 7× (850KB → 6.0MB)
- Allocs/op jumped 12× (5,435 → 66,976) — likely a large struct or slice allocation introduced
📋 Additional Context
- Run ID: §27426858123
- Date: 2026-06-12
- Workflow: Daily CLI Performance
- Also regressing: CompileSimpleWorkflow (+269%), CompileComplexWorkflow (+203%), CompileMemoryUsage (+149%)
- Pattern: All compilation-related benchmarks regressed simultaneously — likely same root cause
Automatically generated by Daily CLI Performance workflow
Generated by ⚡ Daily CLI Performance Agent · 270 AIC · ⌖ 28.9 AIC · ⊞ 23.9K · ◷
📊 Performance Regression Detected
Benchmark: YAMLGeneration
Current Performance: 9,663,952 ns/op (9.66ms)
Historical Average: 3,647,443 ns/op (3.65ms)
Change: +164.9% slower
📈 Detailed Performance Metrics
Performance Comparison
Baseline Targets
💡 Recommended Actions
make bench-memoryto generate memory profilesgo tool pprofto identify hotspots — memory regressed 7× (850KB → 6.0MB)📋 Additional Context
Automatically generated by Daily CLI Performance workflow