Benchmarks

How fast is pnpm, really? We install two real projects with npm, two generations of pnpm, and three pnpm configurations — and install Node.js itself against fnm and nvm.

Data fetched Nov 17, 2026 from pnpm/benchmarks, rebuilt on every deploy.

Package managers

Install Speed

Two projects installed six ways each — the cache and lockfile states you actually end up in, from a fresh clone to a warm re-run.

Tools
Projects
Every bar shares one scale, so scenarios are comparable with each other. Tools stay in the same order in every scenario.

alotta-files

A wide dependency graph of small packages — lots of files to link, little to resolve.

6/6scenarios where pnpm beats npm
57xfaster than npm on “everything warm”
17mspnpm's best run — “everything warm”
cleanA fresh clone. Nothing cached.
npm
45.5s16x slower
pnpm 11
8.22s2.8x slower
pnpm 12
4.70s1.6x slower
pnpm 12 + pnpr
2.91s
pnpm 12 + global store
5.47s1.9x slower
pnpm 12 hoisted
4.78s1.6x slower
lockfileCI, first install.
npm
11.2s4.2x slower
pnpm 11
4.86s1.8x slower
pnpm 12
3.45s1.3x slower
pnpm 12 + pnpr
2.67s
pnpm 12 + global store
3.67s1.4x slower
pnpm 12 hoisted
3.66s1.4x slower
cacheReinstalling without a lockfile.
npm
10.7s18x slower
pnpm 11
3.88s6.6x slower
pnpm 12
1.04s1.8x slower
pnpm 12 + pnpr
885ms1.5x slower
pnpm 12 + global store
592ms
pnpm 12 hoisted
976ms1.6x slower
cache + lockfileReinstalling a project you already have.
npm
6.81s32x slower
pnpm 11
2.38s11x slower
pnpm 12
877ms4.2x slower
pnpm 12 + pnpr
911ms4.3x slower
pnpm 12 + global store
210ms
pnpm 12 hoisted
630ms3.0x slower
everything warmRunning install when nothing changed.
npm
961ms60x slower
pnpm 11
555ms35x slower
pnpm 12
17ms1.1x slower
pnpm 12 + pnpr
16ms
pnpm 12 + global store
60ms3.8x slower
pnpm 12 hoisted
17ms1.1x slower
updateA dependency was bumped in package.json.
npm
4.03s4.4x slower
pnpm 11
3.38s3.7x slower
pnpm 12
926ms
pnpm 12 + pnpr
954ms
pnpm 12 + global store
1.04s1.1x slower
pnpm 12 hoisted
1.23s1.3x slower

Total across all scenarios

  1. pnpm 12 + pnpr8.35sfastest
  2. pnpm 1211.0s1.3x slower
  3. pnpm 12 + global store11.0s1.3x slower
  4. pnpm 12 hoisted11.3s1.4x slower
  5. pnpm 1123.3s2.8x slower
  6. npm1m 19s9.5x slower

All 6 scenarios added up.

Total across all scenarios with usage weights

  1. pnpm 12 + global store19.1sfastest
  2. pnpm 12 + pnpr21.0s1.1x slower
  3. pnpm 12 hoisted23.6s1.2x slower
  4. pnpm 1224.7s1.3x slower
  5. pnpm 111m 1s3.2x slower
  6. npm2m 56s9.2x slower

A typical mix of 20 installs during local development, where the cache is rarely cold: 8× cache + lockfile, 4× cache, 3× everything warm, 2× lockfile, 2× update, 1× clean.

Exact numbers

Install Speed on alotta-files — fastest run per scenario.
Scenarionpmv12.2.2pnpm 11v11.28.12pnpm 12v12.21.0pnpm 12 + pnprv12.21.0pnpm 12 + global storev12.21.0pnpm 12 hoistedv12.21.0
cleanA fresh clone. Nothing cached.45.5s8.22s4.70s2.91s5.47s4.78s
lockfileCI, first install.11.2s4.86s3.45s2.67s3.67s3.66s
cacheReinstalling without a lockfile.10.7s3.88s1.04s885ms592ms976ms
cache + lockfileReinstalling a project you already have.6.81s2.38s877ms911ms210ms630ms
everything warmRunning install when nothing changed.961ms555ms17ms16ms60ms17ms
updateA dependency was bumped in package.json.4.03s3.38s926ms954ms1.04s1.23s
Measured with npm 12.2.2 · pnpm 11 11.28.12 · pnpm 12 12.21.0 · pnpm 12 + pnpr 12.21.0 · pnpm 12 + global store 12.21.0 · pnpm 12 hoisted 12.21.0.

alotta-packages

Fourteen modern toolchains — Angular, Nest, Vite, webpack, Storybook — resolving to about a gigabyte.

6/6scenarios where pnpm beats npm
174xfaster than npm on “everything warm”
16mspnpm's best run — “everything warm”
cleanA fresh clone. Nothing cached.
npm
1m 44s12x slower
pnpm 11
26.9s3.1x slower
pnpm 12
14.4s1.7x slower
pnpm 12 + pnpr
8.55s
pnpm 12 + global store
15.1s1.8x slower
pnpm 12 hoisted
15.5s1.8x slower
cacheReinstalling without a lockfile.
npm
36.8s27x slower
pnpm 11
15.0s11x slower
pnpm 12
3.29s2.4x slower
pnpm 12 + pnpr
2.56s1.8x slower
pnpm 12 + global store
1.39s
pnpm 12 hoisted
3.13s2.3x slower
lockfileCI, first install.
npm
29.7s3.7x slower
pnpm 11
13.3s1.7x slower
pnpm 12
9.01s1.1x slower
pnpm 12 + pnpr
8.04s
pnpm 12 + global store
9.51s1.2x slower
pnpm 12 hoisted
10.9s1.4x slower
cache + lockfileReinstalling a project you already have.
npm
20.5s45x slower
pnpm 11
5.61s12x slower
pnpm 12
2.60s5.7x slower
pnpm 12 + pnpr
3.06s6.8x slower
pnpm 12 + global store
453ms
pnpm 12 hoisted
2.41s5.3x slower
everything warmRunning install when nothing changed.
npm
2.78s174x slower
pnpm 11
566ms35x slower
pnpm 12
16ms
pnpm 12 + pnpr
17ms1.1x slower
pnpm 12 + global store
101ms6.3x slower
pnpm 12 hoisted
17ms1.1x slower
updateA dependency was bumped in package.json.
npm
14.8s7.1x slower
pnpm 11
9.56s4.6x slower
pnpm 12
2.32s1.1x slower
pnpm 12 + pnpr
2.08s
pnpm 12 + global store
2.34s1.1x slower
pnpm 12 hoisted
4.24s2.0x slower

Total across all scenarios

  1. pnpm 12 + pnpr24.3sfastest
  2. pnpm 12 + global store28.9s1.2x slower
  3. pnpm 1231.6s1.3x slower
  4. pnpm 12 hoisted36.2s1.5x slower
  5. pnpm 111m 11s2.9x slower
  6. npm3m 29s8.6x slower

All 6 scenarios added up.

Total across all scenarios with usage weights

  1. pnpm 12 + global store48.3sfastest
  2. pnpm 12 + pnpr1m 4s1.3x slower
  3. pnpm 121m 11s1.5x slower
  4. pnpm 12 hoisted1m 18s1.6x slower
  5. pnpm 112m 59s3.7x slower
  6. npm8m 33s11x slower

A typical mix of 20 installs during local development, where the cache is rarely cold: 8× cache + lockfile, 4× cache, 3× everything warm, 2× lockfile, 2× update, 1× clean.

Exact numbers

Install Speed on alotta-packages — fastest run per scenario.
Scenarionpmv12.2.2pnpm 11v11.28.12pnpm 12v12.21.0pnpm 12 + pnprv12.21.0pnpm 12 + global storev12.21.0pnpm 12 hoistedv12.21.0
cleanA fresh clone. Nothing cached.1m 44s26.9s14.4s8.55s15.1s15.5s
cacheReinstalling without a lockfile.36.8s15.0s3.29s2.56s1.39s3.13s
lockfileCI, first install.29.7s13.3s9.01s8.04s9.51s10.9s
cache + lockfileReinstalling a project you already have.20.5s5.61s2.60s3.06s453ms2.41s
everything warmRunning install when nothing changed.2.78s566ms16ms17ms101ms17ms
updateA dependency was bumped in package.json.14.8s9.56s2.32s2.08s2.34s4.24s
Measured with npm 12.2.2 · pnpm 11 11.28.12 · pnpm 12 12.21.0 · pnpm 12 + pnpr 12.21.0 · pnpm 12 + global store 12.21.0 · pnpm 12 hoisted 12.21.0.
  • Two projects, run separately: "alotta-files" is a wide graph of small packages, "alotta-packages" is fourteen modern toolchains resolving to about a gigabyte. Both are shown because they do not agree — pnpm leads on each, but by different margins, and pnpr gains far more on the larger graph.
  • Within a project the only thing that changes is the package manager, and every manager is measured with the same versions on both projects. Numbers are never combined across projects.
  • Each number is the fastest of the three most recent runs.
  • Everything installs through the same registry over the same emulated link (50ms, 200Mbps), so the times include the round trips a real install pays for.
  • Six scenarios here. The suite measures three more that delete your cache or lockfile but keep node_modules — nobody works that way, so they are left out.
  • pnpm 12 + pnpr is the same version and the same command, with resolution handled by the registry instead of locally.
  • The three columns after pnpm 12 are that same pnpm 12 configured differently — a global virtual store, a hoisted node_modules, and registry-side resolution. They are shown to make the cost of each setting visible, and are left out of the headline numbers above, which describe pnpm as it installs by default.
Node.js version managers

Node.js Version Management

pnpm installs and switches Node.js versions itself, so you may not need a version manager at all. Here it is against fnm and nvm.

Every bar shares one scale, so scenarios are comparable with each other. Tools stay in the same order in every scenario.
2/3scenarios where pnpm is fastest
27xfaster than nvm on “install (warm store)”
8mspnpm's best run — “run in project”
install (clean)Install Node.js 24, nothing cached.
pnpm
1.46s
fnm
2.98s2.0x slower
nvm
2.53s1.7x slower
install (warm store)Install a version you had before.
pnpm
71ms
fnm
2.95s42x slower
nvm
1.92s27x slower
run in projectRun node in a project pinned to Node.js 22.
pnpm
8ms1.6x slower
fnm
5ms
nvm
52ms11x slower

Total across all scenarios

  1. pnpm1.54sfastest
  2. nvm4.49s2.9x slower
  3. fnm5.94s3.9x slower

All 3 scenarios added up.

Exact numbers

Node.js Version Management — fastest run per scenario.
Scenariopnpmv12.21.0fnmv1.39.0nvmv0.41.0
install (clean)Install Node.js 24, nothing cached.1.46s2.98s2.53s
install (warm store)Install a version you had before.71ms2.95s1.92s
run in projectRun node in a project pinned to Node.js 22.8ms5ms52ms
Measured with pnpm 12.21.0 · fnm 1.39.0 · nvm 0.41.0.
  • pnpm keeps Node.js in its store, so a version it has seen before needs no download.
  • There is no switch command — the node on your PATH is whatever the project asks for.
  • Timed inside a shell with $EPOCHREALTIME, because nvm is a shell function rather than a binary.

How these numbers are produced

Every tool runs on the same machine against the same project, and the timings are committed to pnpm/benchmarks. This page reads them at build time and picks the newest version of each tool.

This is one project on one machine — your numbers will differ. Run pnpm run benchmark to see your own.