chore: refresh benchmarks for v1.17.1#820
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR updates benchmark measurements by refreshing test results with new performance data, updating the pnpm tool version from 11.4.0 to 11.5.0, and syncing the README to report the newly measured speedup multipliers. ChangesBenchmark Results Update
🎯 1 (Trivial) | ⏱️ ~3 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Greptile SummaryRefreshes
Confidence Score: 5/5Safe to merge — changes are limited to benchmark data and marketing copy, with no logic or functional code touched. Both files are data-only. The integer values, statistical text labels, mean/stddev fields, and README ratios are all arithmetically consistent with each other. The warm-cache aube improvement (−46%) is notable but falls within what a significant release optimisation could produce, and the PR description explicitly flags it for human review before merge. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "chore: refresh benchmarks" | Re-trigger Greptile |
🤖 Refreshed benchmarks
benchmarks/results.jsonwas pinned to aube1.16.1; the workspace is now1.17.1. 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 3x -> 5x; warm installs vs pnpm 5x -> 9x; repeat test vs Bun 4x -> 5x; repeat test vs pnpm 30x -> 38x.
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.Summary by CodeRabbit