Repository navigation
chore: refresh benchmarks for v2.2.3 - #1417
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe benchmark results metadata, tool versions, and measurements were refreshed. The README now reflects the updated warm-install and repeat-test speedup figures. ChangesBenchmark Refresh
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR refreshes benchmark artifacts and README performance ratios without changing runtime or installation behavior; no actionable merge-blocking risk remains beyond normal checks and review. Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.) Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryRefreshes published benchmark data for aube 2.2.3 and updates the README’s derived performance claims.
Confidence Score: 5/5The PR appears safe to merge with no actionable correctness or security issues identified. The refreshed benchmark values agree with their raw statistics, the README ratios are correctly derived from those values, and the data remains compatible with existing consumers and validation. Important Files Changed
Reviews (1): Last reviewed commit: "chore: refresh benchmarks" | Re-trigger Greptile |
Instruction counts
No instruction-count regression above 1%. Only instruction counts gate. Wall clock is shown for context — on identical hardware it moves 4-20% run to run. Measured by tak — instruction-counted CLI benchmarks, stored in this repository's git notes.
|
🤖 Refreshed benchmarks
benchmarks/results.jsonwas pinned to aube2.2.0; the workspace is now2.2.3. Re-ranmise run bench:bumpon the hermetic Verdaccio registry (500mbit / 50ms per the mise task) and regeneratedbenchmarks/results.jsonplus the READMEBENCH_RATIOSblock. The benchmark matrix pins aube's GVS mode vianpm_config_enable_global_virtual_store=true|false(the auto-synthesized env alias for theenableGlobalVirtualStoresetting), so GitHub Actions' inheritedCI=trueenvironment does not change whether aube runs with GVS enabled or disabled.Benchmark changes
Versions:
Public ratios: warm installs vs Bun 2x -> 3x; warm installs vs pnpm 6x -> 9x; repeat test vs Bun 1.9x -> 2x; repeat test vs pnpm 21x -> 27x.
Review the numbers before merging — if anything looks wildly off vs. the previous release, investigate before landing. Hermetic proxy jitter or an npmjs uplink hiccup can occasionally skew results.
Once merged to main, the updated bench results flow into the next
release-plz-prrun automatically.Generated by the
bench-refreshworkflow.Note
Low Risk
Documentation and benchmark artifact updates only; no runtime or install logic changes.
Overview
Refreshes published benchmark numbers for aube 2.2.3 (from 2.2.0) by re-running the benchmark suite and updating
benchmarks/results.jsonwith a new timestamp, tool versions (deno 2.9.6, pnpm 11.25.0), and revised timings across warm/cold install and repeat install && test scenarios.The README
BENCH_RATIOSblock is regenerated so marketing ratios match the new data: warm installs are now cited as ~9× vs pnpm and ~3× vs Bun (up from 6× and 2×), and repeat test commands up to 27× vs pnpm and 2× vs Bun (up from 21× and 1.9×). Aube’s own warm-install and repeat-test numbers improved modestly in this run; pnpm warm-install regressed in the benchmark matrix, which drives the higher relative ratios.Reviewed by Cursor Bugbot for commit 66db4d7. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
Documentation
Chores