Skip to content

[performance] Regression in YAMLGeneration: 21.7% slower #29779

Closed

Description

@github-actions

📊 Performance Regression Detected

Benchmark: YAMLGeneration

Current Performance: 1,804,146 ns/op (1.80ms)
Historical Average: 1,482,683 ns/op (1.48ms)
Change: +21.7% slower
Historical Data Points: 2

📈 Detailed Performance Metrics

Performance Comparison

  • ns/op: 1,804,146 (was 1,482,683)
  • Change: +21.7%
  • Memory: 959,309 B/op, 4,123 allocs/op

💡 Recommended Actions

  1. Review recent changes to YAML generation in pkg/workflow/
  2. Run make bench-memory to generate memory profiles
  3. Use go tool pprof to identify hotspots in YAML output code
  4. Compare with previous benchmark results using benchstat
📋 Additional Context
  • Run ID: §25254840589
  • Date: 2026-05-02
  • Historical Runs Compared: 2 (2026-04-30)

Automatically generated by Daily CLI Performance workflow

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

  • expires on May 4, 2026, 3:12 PM UTC

Activity

  1. github-actions commented on May 3, 2026

    @github-actions
    ContributorAuthor

    🍪 Issue Monster selected this for Copilot

    I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

    If assignment succeeds, 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 · ● 26.2K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions