Skip to content

[performance] Regression in Validation: +38.9% slower #29404

Closed

Description

@github-actions

📊 Performance Regression Detected

Benchmark: BenchmarkValidation

Current Performance: 16,180 ns/op (16.18μs)
Historical Average: 11,648 ns/op (11.65μs)
Change: +38.9% slower
Data Points: 2

⚠️ Note: Only 2 data points available (both from 2026-04-30). This regression may reflect run-to-run variance rather than a code regression. Monitor subsequent runs to confirm.

📈 Detailed Performance Metrics

Performance Comparison

  • ns/op: 16,180 (was 11,648)
  • B/op: 1,256
  • allocs/op: 11
  • Change: +38.9%

Absolute Timings

Both values are in the microsecond range and well within acceptable bounds for validation. The percentage change is high but the absolute difference is only ~4.5μs.

💡 Recommended Actions

  1. Monitor subsequent benchmark runs to confirm if this is a persistent regression
  2. Review recent changes to workflow validation logic
  3. Run make bench-memory to generate memory profiles
  4. Use go tool pprof to identify performance hotspots
📋 Additional Context
  • Run ID: §25194552853
  • Date: 2026-04-30
  • Workflow: Daily CLI Performance

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

  • expires on May 2, 2026, 11:39 PM UTC

Activity

  1. github-actions commented on Apr 30, 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 · ● 20.5K · ◷

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