Skip to content

[performance] Regression in CompileMCPWorkflow: 76.6% slower #29945

Closed

Description

@github-actions

Benchmark: CompileMCPWorkflow

Current Performance: 501,881 ns/op (501.88μs)
Historical Average: 284,219 ns/op (284.22μs)
Change: +76.6% slower

📈 Detailed Performance Metrics

Performance Comparison

  • ns/op: 501,881 (was 284,219)
  • Change: +76.6%
  • Historical Data Points: 3
  • Memory: 106,864 B/op
  • Allocations: 2,027 allocs/op

Historical Data

Date ns/op
2026-04-30 292,618
2026-04-30 278,983
2026-05-02 281,057
2026-05-03 501,881

Baseline Targets

  • MCP-heavy workflows: <1s — still within target, but significant increase

💡 Recommended Actions

  1. Review recent changes to the MCP workflow compilation pipeline
  2. Run make bench-memory to generate memory profiles
  3. Use go tool pprof to identify hotspots
📋 Additional Context

Automatically generated by Daily CLI Performance workflow

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

  • expires on May 5, 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 · ● 17.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