📊 Performance Regression Detected
Benchmark: BenchmarkExtractWorkflowNameFromFile
Current Performance: 82,538 ns/op (82.54µs)
Historical Average: 68,885 ns/op (68.89µs)
Change: +19.8% slower
Data Points: 1 historical entry (2026-03-12)
📈 Detailed Performance Metrics
Performance Comparison
| Metric |
Yesterday |
Today |
Change |
| ns/op |
68,885 |
82,538 |
+19.8% |
| B/op |
N/A |
5,864 |
— |
| allocs/op |
N/A |
116 |
— |
Baseline Targets
- Simple workflows: <100ms (well within range)
- Complex workflows: <500ms (well within range)
- MCP-heavy workflows: <1s (well within range)
ExtractWorkflowNameFromFile is a CLI helper, no explicit target — but regression threshold is 10%
🔍 Context
This benchmark measures how quickly the CLI extracts workflow names from file paths. A regression here could impact workflows that enumerate or reference workflow files by name.
Note: this comparison is based on 1 historical data point — while the threshold has been crossed (+19.8% > 10%), it should be monitored over the next few runs to confirm this is a real regression and not measurement noise.
💡 Recommended Actions
- Review recent changes to the workflow name extraction logic in
pkg/cli/ or pkg/workflow/
- Run
go test -v -run "TestExtractWorkflowName" ./pkg/cli/ to verify correctness
- Run
go test -bench=BenchmarkExtractWorkflowNameFromFile ./pkg/cli/ -benchtime=10s for a more stable measurement
- Compare with previous benchmark results using
benchstat
📋 Full Benchmark Run Context (2026-03-13)
| Benchmark |
ns/op |
Change |
Status |
| CompileSimpleWorkflow |
22,680,852 |
+2.0% |
✓ Stable |
| CompileComplexWorkflow |
5,791,573 |
+2.4% |
✓ Stable |
| CompileMCPWorkflow |
15,948,627 |
+1.9% |
✓ Stable |
| CompileMemoryUsage |
6,481,048 |
+4.0% |
✓ Stable |
| ParseWorkflow |
7,665,307 |
-14.8% |
✨ Improvement |
| Validation |
6,062,525 |
-7.6% |
✨ Improvement |
| YAMLGeneration |
12,245,479 |
+1.6% |
✓ Stable |
| ExtractWorkflowNameFromFile |
82,538 |
+19.8% |
⚠️ Regression |
| FindIncludesInContent |
32,851 |
-16.6% |
✨ Improvement |
References:
Generated by Daily CLI Performance Agent · ◷
📊 Performance Regression Detected
Benchmark:
BenchmarkExtractWorkflowNameFromFileCurrent Performance: 82,538 ns/op (82.54µs)
Historical Average: 68,885 ns/op (68.89µs)
Change: +19.8% slower
Data Points: 1 historical entry (2026-03-12)
📈 Detailed Performance Metrics
Performance Comparison
Baseline Targets
ExtractWorkflowNameFromFileis a CLI helper, no explicit target — but regression threshold is 10%🔍 Context
This benchmark measures how quickly the CLI extracts workflow names from file paths. A regression here could impact workflows that enumerate or reference workflow files by name.
Note: this comparison is based on 1 historical data point — while the threshold has been crossed (+19.8% > 10%), it should be monitored over the next few runs to confirm this is a real regression and not measurement noise.
💡 Recommended Actions
pkg/cli/orpkg/workflow/go test -v -run "TestExtractWorkflowName" ./pkg/cli/to verify correctnessgo test -bench=BenchmarkExtractWorkflowNameFromFile ./pkg/cli/ -benchtime=10sfor a more stable measurementbenchstat📋 Full Benchmark Run Context (2026-03-13)
References: