Skip to content

[performance] Regression in YAMLGeneration: 33.2% slower #41259

Description

@github-actions

📊 Performance Regression Detected

Benchmark: YAMLGeneration

Current Performance: 7,895,809 ns/op (7.90ms)
Historical Average: 5,929,595 ns/op (5.93ms)
Change: +33.2% slower

⚠️ Note: This comparison is based on 1 historical data point (2026-06-23). More data points will improve confidence.

📈 Detailed Performance Metrics

Performance Comparison

  • ns/op: 7,895,809 (was 5,929,595)
  • B/op: 986,533 (was 951,197)
  • allocs/op: 5,565 (was 5,501)
  • Change: +33.2%
  • Historical Data Points: 1

Baseline Targets

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

Other Benchmarks (same run)

Benchmark Status Change
CompileSimpleWorkflow ✓ Stable -1.8%
CompileComplexWorkflow ✨ Improvement -16.3%
CompileMCPWorkflow ✨ Improvement -33.9%
CompileMemoryUsage ✓ Stable -4.8%
ParseWorkflow ✨ Improvement -6.1%
Validation ✨ Improvement -25.7%
ExtractWorkflowNameFromFile ✓ Stable +0.4%

💡 Recommended Actions

  1. Review recent changes to the YAML generation pipeline
  2. Run make bench-memory to generate memory profiles
  3. Use go tool pprof to identify hotspots
  4. Compare with previous benchmark results: benchstat
📋 Additional Context

Automatically generated by Daily CLI Performance workflow

Generated by ⚡ Daily CLI Performance Agent · 60.5 AIC · ⌖ 24.4 AIC · ⊞ 11.4K ·

  • expires on Jun 26, 2026, 7:49 AM UTC-08:00

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions