Skip to content

chore: refresh benchmarks for v1.18.0#841

Merged
jdx merged 1 commit into
mainfrom
bench-refresh
Jun 5, 2026
Merged

chore: refresh benchmarks for v1.18.0#841
jdx merged 1 commit into
mainfrom
bench-refresh

Conversation

@mise-en-dev

@mise-en-dev mise-en-dev commented Jun 5, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Collaborator

🤖 Refreshed benchmarks

benchmarks/results.json was pinned to aube 1.17.1; the workspace is now 1.18.0. Re-ran mise run bench:bump on the hermetic Verdaccio registry (500mbit / 50ms per the mise task) and regenerated benchmarks/results.json plus the README BENCH_RATIOS block. The benchmark matrix pins aube's GVS mode via npm_config_enable_global_virtual_store=true|false (the auto-synthesized env alias for the enableGlobalVirtualStore setting), so GitHub Actions' inherited CI=true environment does not change whether aube runs with GVS enabled or disabled.

Benchmark changes

Versions:

  • aube: 1.17.1 -> 1.18.0
  • deno: 2.8.1 -> 2.8.2
  • pnpm: 11.5.0 -> 11.5.2
  • yarn: 4.15.0 -> 4.16.0

Public ratios: warm installs vs Bun 5x -> 7x; warm installs vs pnpm 9x -> 9x; repeat test vs Bun 5x -> 5x; repeat test vs pnpm 38x -> 37x.

Benchmark aube bun deno pnpm npm yarn
Fresh install (warm cache) 300ms -> 272ms (-9%) 1483ms -> 2003ms (+35%) 1702ms -> 1327ms (-22%) 2628ms -> 2341ms (-11%) 6946ms -> 7141ms (+3%) 8003ms -> 8856ms (+11%)
Fresh install (cold cache) 6861ms -> 7950ms (+16%) 4896ms -> 5777ms (+18%) 7167ms -> 8153ms (+14%) 16439ms -> 15870ms (-3%) 9171ms -> 9507ms (+4%) 11806ms -> 13192ms (+12%)
npm install && npm run test 9ms -> 9ms (0%) 43ms -> 41ms (-5%) 78ms -> 84ms (+8%) 340ms -> 335ms (-1%) 701ms -> 745ms (+6%) 1222ms -> 1175ms (-4%)

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-pr run automatically.

Generated by the bench-refresh workflow.

Summary by CodeRabbit

  • Documentation

    • Updated README with revised benchmark performance claim for pnpm package manager.

  • Chores

    • Refreshed benchmark results data with new measurements and statistical calculations across multiple package managers.

@greptile-apps

greptile-apps Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Refreshes benchmark data from aube 1.17.1 to 1.18.0, updating timing measurements for all six package managers and bumping deno, pnpm, and yarn to their latest patch versions.

  • benchmarks/results.json gets a new timestamp, version map, and three full benchmark rows (warm-cache, cold-cache, repeat-test) with updated mean/stddev/min/max statistics; all rounded values entries are consistent with Math.round(mean * 1000).
  • README.md updates the BENCH_RATIOS block to reflect that aube is now ~7x faster than Bun on warm installs (up from 5x) and ~37x faster than pnpm on repeat tests (down from 38x); both figures match the new JSON data.

Confidence Score: 5/5

Safe to merge; changes are purely benchmark data and a two-sentence README update with no logic changes.

All integer values in results.json round-trip correctly from their corresponding mean fields, and the README ratios (7x Bun, 9x pnpm, 37x pnpm repeat, 5x Bun repeat) match the new timing data. The cold-cache regression for aube (+16%) is explicitly called out in the PR description and is within the measured standard deviation range. No code is changed.

No files require special attention.

Important Files Changed

Filename Overview
benchmarks/results.json Benchmark data refreshed for aube 1.18.0; all integer values fields are consistent with Math.round(mean * 1000) across all three benchmark rows and six managers.
README.md BENCH_RATIOS block updated; stated ratios (7x Bun, 9x pnpm, 37x pnpm repeat, 5x Bun repeat) match the new JSON values within normal rounding.

Reviews (1): Last reviewed commit: "chore: refresh benchmarks" | Re-trigger Greptile

@coderabbitai

coderabbitai Bot commented Jun 5, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c4cc82d9-bbf6-4ff4-b85c-e00a2fbc8caf

📥 Commits

Reviewing files that changed from the base of the PR and between 215681f and afe2870.

📒 Files selected for processing (2)
  • README.md
  • benchmarks/results.json
📝 Walkthrough

Walkthrough

This PR refreshes benchmark measurement data in benchmarks/results.json with updated timing results across package managers, and updates the README to reflect the revised pnpm speedup figure from "up to 38x" to "up to 37x" for warm repeat installations.

Changes

Benchmark Update

Layer / File(s) Summary
Benchmark results refresh
benchmarks/results.json		 The updated timestamp, versions metadata for multiple package managers, and benchmark measurements (values and stats fields including mean, stddev, min, max) are refreshed for gvs-warm, gvs-cold, and install-test test rows.
README benchmark documentation
README.md		 The README's "Fast installs" claim is adjusted to report the updated pnpm warm-repeat speedup as "up to 37x" instead of "up to 38x".

Possibly related PRs

  • endevco/aube#820: Updates the same pnpm benchmark speedup figure in README and refreshes the same benchmark data in benchmarks/results.json.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🐰 Benchmarks hopped and renewed,
With timings fresh and figures turned,
From 38 to 37 times fast,
These swifter speeds are here to last!
✨ whisker twitch ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore: refresh benchmarks for v1.18.0' directly and clearly describes the main change: updating benchmark data and documentation for version 1.18.0.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bench-refresh

Comment @coderabbitai help to get the list of available commands and usage tips.

@jdx jdx merged commit e1e2fb7 into main Jun 5, 2026
18 checks passed
@jdx jdx deleted the bench-refresh branch June 5, 2026 15:37
@greptile-apps greptile-apps Bot mentioned this pull request Jun 5, 2026
Merged
@BrewTestBot BrewTestBot mentioned this pull request Jun 7, 2026
Merged
@coderabbitai coderabbitai Bot mentioned this pull request Jun 12, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mise-en-dev @jdx