Add ci command benchmarks to package manager suite - #167
Open
vltbaudbot wants to merge 1 commit into
Open
Conversation
Add a new 'ci' benchmark variation that tests each package manager's CI/frozen-lockfile install command: - npm ci - yarn install --frozen-lockfile (classic) - yarn install --immutable (berry/zpm) - pnpm install --frozen-lockfile - pnpm 12 install --frozen-lockfile (pacquet) - vlt ci - bun install --frozen-lockfile - deno install --frozen - aube ci The ci variation measures the production/CI-oriented counterpart to regular install. Each PM's prepare step generates a lockfile via regular install, then cleans node_modules — simulating a CI pipeline where the lockfile is committed and caches may be restored, but node_modules is absent. Changes: - scripts/variations/ci.sh: New variation script with per-PM ci commands and prepare steps that generate lockfiles before each measured run - scripts/benchmark.sh: Add ci case to variation dispatcher - bench: Add ci to AVAILABLE_VARIATIONS list - .github/workflows/benchmark.yaml: Add ci to matrix variations and partial-run detection defaults - scripts/process-results.sh: Add ci to the variation processing loop - scripts/generate-chart.js: Add ci to the chart data variations list - app/src/types/chart-data.ts: Add ci to Variation type and validation - app/src/lib/utils.ts: Add ci to variation categories, sort order, and average calculation - app/src/hooks/use-history-data.ts: Include ci in the package management average history computation Co-authored-by: Evert Pot <me@evertpot.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
cibenchmark variation that tests each package manager's CI/frozen-lockfile install command — the production-oriented counterpart to regularinstall.CI commands benchmarked
npm ciyarn install --frozen-lockfileyarn install --immutableyarn install --immutablepnpm install --frozen-lockfilepnpm install --frozen-lockfilevlt cibun install --frozen-lockfiledeno install --frozenaube ciHow it works
The
civariation differs fromcache+lockfilein that it uses each PM's dedicated CI command (which enforces a frozen lockfile) rather than a regularinstall. Each PM's prepare step:installto generate the lockfile and populate cachesThe measured command then runs the CI variant, simulating a typical CI pipeline.
Files changed
scripts/variations/ci.sh— New variation scriptscripts/benchmark.sh— Add ci case to dispatcherbench— Add ci to available variations.github/workflows/benchmark.yaml— Add ci to matrix & partial-run detectionscripts/process-results.sh— Add ci to processing loopscripts/generate-chart.js— Add ci to chart data generationapp/src/types/chart-data.ts— Add ci to TypeScript typesapp/src/lib/utils.ts— Add ci to categories, sort order, and averagesapp/src/hooks/use-history-data.ts— Include ci in history averagesCo-authored-by: Evert Pot me@evertpot.com