Benchmark: BenchmarkExtractWorkflowNameFromFile
Current Performance: 17,165 ns/op (17.16μs)
Historical Average: 14,190 ns/op (14.19μs)
Change: +21.0% slower
Historical Data Points: 2
📈 Detailed Performance Metrics
Performance Comparison
- ns/op: 17,165 (was 14,190)
- Change: +21.0%
- Memory: 4,362 B/op, 8 allocs/op
Historical Values
| Date |
ns/op |
| 2026-05-08 |
12,243 |
| 2026-05-09 |
16,138 |
| 2026-05-10 (today) |
17,165 |
Note: Only 2 historical data points available. The benchmark was introduced on 2026-05-08. With limited history, this regression threshold crossing may reflect normal variance. Monitor closely.
💡 Recommended Actions
- Monitor over the next few runs — only 2 historical data points, so confidence is low
- If regression persists: review recent changes to
ExtractWorkflowNameFromFile or related file path utilities
- Run
make bench-memory to generate memory profiles if needed
📋 Additional Context
- Run ID: §25632111265
- Date: 2026-05-10
- Also noted: CompileSimpleWorkflow improved -29.9%, FindIncludesInContent improved -31.2%
Generated by Daily CLI Performance Agent · ● 8.8M · ◷
Benchmark: BenchmarkExtractWorkflowNameFromFile
Current Performance: 17,165 ns/op (17.16μs)
Historical Average: 14,190 ns/op (14.19μs)
Change: +21.0% slower
Historical Data Points: 2
📈 Detailed Performance Metrics
Performance Comparison
Historical Values
Note: Only 2 historical data points available. The benchmark was introduced on 2026-05-08. With limited history, this regression threshold crossing may reflect normal variance. Monitor closely.
💡 Recommended Actions
ExtractWorkflowNameFromFileor related file path utilitiesmake bench-memoryto generate memory profiles if needed📋 Additional Context