[daily-cli-performance] Daily CLI Performance Report - 2026-08-19 #54034
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-22T15:14:32.854Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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