Skip to content

[performance] Regression in FindIncludesInContent: 27.5% slower #26167

@github-actions

Description

@github-actions

📊 Performance Regression Detected

Benchmark: BenchmarkFindIncludesInContent

Current Performance: 34,808 ns/op (34.81μs)
Historical Average: 27,304 ns/op (27.30μs)
Change: +27.5% slower
Historical Data Points: 4 runs

📈 Detailed Performance Metrics

Performance Comparison

  • ns/op: 34,808 (was ~27,304 average)
  • B/op: 14,557
  • allocs/op: 52
  • Change: +27.5% (threshold: 10%)

Baseline Targets

  • Simple workflows: <100ms ✅
  • Complex workflows: <500ms ✅
  • MCP-heavy workflows: <1s ✅
  • FindIncludesInContent: regression detected

💡 Recommended Actions

  1. Review recent changes to FindIncludesInContent in the CLI/workflow parser
  2. Run make bench-memory to generate memory profiles
  3. Use go tool pprof to identify hotspots
  4. Compare with previous benchmark results using benchstat
  5. Check if regex compilation or string scanning patterns changed recently
📋 Additional Context

Other Benchmark Results (2026-04-14)

All compilation benchmarks showed improvements this run:

Benchmark Current Historical Avg Change
CompileSimpleWorkflow 5.11ms 5.73ms -11.0% ✨
CompileComplexWorkflow 8.56ms 9.66ms -11.4% ✨
CompileMCPWorkflow 5.04ms 6.83ms -26.2% ✨
CompileMemoryUsage 8.10ms 9.60ms -15.6% ✨
ParseWorkflow 1.17ms 1.22ms -4.2% ✓
Validation 1.78ms 1.97ms -9.5% ✨
YAMLGeneration 5.30ms 5.41ms -2.0% ✓
ExtractWorkflowNameFromFile 16.58μs 17.73μs -6.5% ✨
FindIncludesInContent 34.81μs 27.30μs +27.5% ⚠️

References:

Generated by Daily CLI Performance Agent · ● 831.4K ·

  • expires on Apr 16, 2026, 5:56 AM UTC

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    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