You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This run followed a ~6-week gap since the last recorded benchmark (2026-07-06 → 2026-08-19), during which only a single commit touched pkg/workflow/pkg/cli. The Go module cache and build cache in this sandbox had to be freshly initialized (GOCACHE/GOMODCACHE redirected due to permission restrictions on the default $HOME/go), forcing cold compilation/module downloads during the run. The three flagged "regressions" below (CompileMCPWorkflow +1012%, ParseWorkflow +219%, ExtractWorkflowNameFromFile +961%) are implausibly large for a single commit and are most consistent with cold-cache/I/O overhead rather than a genuine code regression. No regression issues are being opened for this run; recommend re-running benchmarks with a warm cache to confirm before treating these as real.
📈 Detailed Benchmark Results
✓ CompileComplexWorkflow
Current: 5.68ms
Historical Median: 5.62ms
Change: +1.1%
Memory: 2110993 B/op
Allocations: 16486 allocs/op
Status: ✓ STABLE: 1.1% change from historical average
⚠️ CompileMCPWorkflow
Current: 3.77ms
Historical Median: 338.90μs
Change: +1012.2%
Memory: 1334876 B/op
Allocations: 12594 allocs/op
Status: ⚠️ REGRESSION: 1012.2% slower than historical average
✨ CompileMemoryUsage
Current: 4.63ms
Historical Median: 4.92ms
Change: -5.8%
Memory: 1920060 B/op
Allocations: 14617 allocs/op
Status: ✅ IMPROVEMENT: -5.8% faster than historical average
✓ CompileSimpleWorkflow
Current: 3.94ms
Historical Median: 4.00ms
Change: -1.6%
Memory: 1322734 B/op
Allocations: 10923 allocs/op
Status: ✓ STABLE: -1.5% change from historical average
⚠️ ExtractWorkflowNameFromFile
Current: 76.96μs
Historical Median: 7.25μs
Change: +961.1%
Memory: 216 B/op
Allocations: 4 allocs/op
Status: ⚠️ REGRESSION: 961.1% slower than historical average
✨ FindIncludesInContent
Current: 150.2ns
Historical Median: 162ns
Change: -7.6%
Memory: 64 B/op
Allocations: 1 allocs/op
Status: ✅ IMPROVEMENT: -7.6% faster than historical average
⚠️ ParseWorkflow
Current: 860.54μs
Historical Median: 270.10μs
Change: +218.6%
Memory: 285142 B/op
Allocations: 5530 allocs/op
Status: ⚠️ REGRESSION: 218.6% slower than historical average
✨ Validation
Current: 14.22μs
Historical Median: 29.11μs
Change: -51.1%
Memory: 1426 B/op
Allocations: 67 allocs/op
Status: ✅ IMPROVEMENT: -51.1% faster than historical average
✨ YAMLGeneration
Current: 3.26ms
Historical Median: 3.92ms
Change: -16.9%
Memory: 1296542 B/op
Allocations: 10378 allocs/op
Status: ✅ IMPROVEMENT: -16.9% faster than historical average
📉 Historical Comparisons
Trend Analysis
⚠️ Regressions (suspected environment noise, not filed as issues)
CompileMCPWorkflow: +1012.2% slower (was 338.90μs, now 3.77ms)
ParseWorkflow: +218.6% slower (was 270.10μs, now 860.54μs)
ExtractWorkflowNameFromFile: +961.1% slower (was 7.25μs, now 76.96μs)
✨ Improvements
CompileMemoryUsage: -5.8% faster (was 4.92ms, now 4.63ms)
Validation: -51.1% faster (was 29.11μs, now 14.22μs)
YAMLGeneration: -16.9% faster (was 3.92ms, now 3.26ms)
FindIncludesInContent: -7.6% faster (was 162ns, now 150.2ns)
💡 Recommendations
Re-run make bench-performance on a runner with a warm Go build/module cache to confirm whether the flagged regressions persist
Continue monitoring performance daily; magnitudes above ~900% for isolated benchmarks should be treated as environment/methodology anomalies until reproduced
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
📊 Performance Summary
Date: 2026-08-19⚠️ 3 regression(s) detected (suspected environment noise — see below)
Analysis Status:
🎯 Key Metrics
This run followed a ~6-week gap since the last recorded benchmark (2026-07-06 → 2026-08-19), during which only a single commit touched
pkg/workflow/pkg/cli. The Go module cache and build cache in this sandbox had to be freshly initialized (GOCACHE/GOMODCACHEredirected due to permission restrictions on the default$HOME/go), forcing cold compilation/module downloads during the run. The three flagged "regressions" below (CompileMCPWorkflow+1012%,ParseWorkflow+219%,ExtractWorkflowNameFromFile+961%) are implausibly large for a single commit and are most consistent with cold-cache/I/O overhead rather than a genuine code regression. No regression issues are being opened for this run; recommend re-running benchmarks with a warm cache to confirm before treating these as real.📈 Detailed Benchmark Results
✓ CompileComplexWorkflow
✨ CompileMemoryUsage
✓ CompileSimpleWorkflow
✨ FindIncludesInContent
✨ Validation
✨ YAMLGeneration
📉 Historical Comparisons
Trend Analysis
✨ Improvements
💡 Recommendations
make bench-performanceon a runner with a warm Go build/module cache to confirm whether the flagged regressions persistAll reactions