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 22, 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
37xfaster than npm on “everything warm”
16mspnpm's best run — “everything warm”
cleanA fresh clone. Nothing cached.
npm
43.1s18x slower
pnpm 11
6.63s2.8x slower
pnpm 12
4.03s1.7x slower
pnpm 12 + pnpr
2.37s
pnpm 12 + global store
4.07s1.7x slower
pnpm 12 hoisted
4.26s1.8x slower
lockfileCI, first install.
npm
10.2s4.9x slower
pnpm 11
4.34s2.1x slower
pnpm 12
3.16s1.5x slower
pnpm 12 + pnpr
2.10s
pnpm 12 + global store
3.14s1.5x slower
pnpm 12 hoisted
3.36s1.6x slower
cacheReinstalling without a lockfile.
npm
7.27s17x slower
pnpm 11
2.89s6.6x slower
pnpm 12
747ms1.7x slower
pnpm 12 + pnpr
439ms
pnpm 12 + global store
632ms1.4x slower
pnpm 12 hoisted
658ms1.5x slower
cache + lockfileReinstalling a project you already have.
npm
4.45s24x slower
pnpm 11
1.65s8.8x slower
pnpm 12
407ms2.2x slower
pnpm 12 + pnpr
410ms2.2x slower
pnpm 12 + global store
187ms
pnpm 12 hoisted
386ms2.1x slower
everything warmRunning install when nothing changed.
npm
588ms37x slower
pnpm 11
399ms25x slower
pnpm 12
16ms
pnpm 12 + pnpr
17ms1.1x slower
pnpm 12 + global store
62ms3.9x slower
pnpm 12 hoisted
16ms
updateA dependency was bumped in package.json.
npm
2.78s3.7x slower
pnpm 11
2.47s3.3x slower
pnpm 12
783ms
pnpm 12 + pnpr
759ms
pnpm 12 + global store
784ms
pnpm 12 hoisted
978ms1.3x slower

Total across all scenarios

  1. pnpm 12 + pnpr6.09sfastest
  2. pnpm 12 + global store8.88s1.5x slower
  3. pnpm 129.14s1.5x slower
  4. pnpm 12 hoisted9.65s1.6x slower
  5. pnpm 1118.4s3.0x slower
  6. npm1m 8s11x slower

All 6 scenarios added up.

Total across all scenarios with usage weights

  1. pnpm 12 + pnpr13.2sfastest
  2. pnpm 12 + global store16.1s1.2x slower
  3. pnpm 1218.2s1.4x slower
  4. pnpm 12 hoisted18.7s1.4x slower
  5. pnpm 1146.2s3.5x slower
  6. npm2m 16s10x 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.3pnpm 11v11.28.13pnpm 12v12.23.0pnpm 12 + pnprv12.23.0pnpm 12 + global storev12.23.0pnpm 12 hoistedv12.23.0
cleanA fresh clone. Nothing cached.43.1s6.63s4.03s2.37s4.07s4.26s
lockfileCI, first install.10.2s4.34s3.16s2.10s3.14s3.36s
cacheReinstalling without a lockfile.7.27s2.89s747ms439ms632ms658ms
cache + lockfileReinstalling a project you already have.4.45s1.65s407ms410ms187ms386ms
everything warmRunning install when nothing changed.588ms399ms16ms17ms62ms16ms
updateA dependency was bumped in package.json.2.78s2.47s783ms759ms784ms978ms
Measured with npm 12.2.3 · pnpm 11 11.28.13 · pnpm 12 12.23.0 · pnpm 12 + pnpr 12.23.0 · pnpm 12 + global store 12.23.0 · pnpm 12 hoisted 12.23.0.

alotta-packages

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

6/6scenarios where pnpm beats npm
72xfaster than npm on “everything warm”
20mspnpm's best run — “everything warm”
cleanA fresh clone. Nothing cached.
npm
1m 36s14x slower
pnpm 11
20.4s3.0x slower
pnpm 12
13.1s1.9x slower
pnpm 12 + pnpr
6.74s
pnpm 12 + global store
12.8s1.9x slower
pnpm 12 hoisted
13.8s2.0x slower
lockfileCI, first install.
npm
27.3s4.3x slower
pnpm 11
11.1s1.7x slower
pnpm 12
8.59s1.3x slower
pnpm 12 + pnpr
6.42s
pnpm 12 + global store
8.70s1.4x slower
pnpm 12 hoisted
9.22s1.4x slower
cacheReinstalling without a lockfile.
npm
23.6s22x slower
pnpm 11
9.87s9.2x slower
pnpm 12
1.61s1.5x slower
pnpm 12 + pnpr
1.07s
pnpm 12 + global store
1.18s1.1x slower
pnpm 12 hoisted
1.79s1.7x slower
cache + lockfileReinstalling a project you already have.
npm
12.6s27x slower
pnpm 11
3.17s6.7x slower
pnpm 12
1.17s2.5x slower
pnpm 12 + pnpr
1.06s2.2x slower
pnpm 12 + global store
471ms
pnpm 12 hoisted
1.91s4.1x slower
everything warmRunning install when nothing changed.
npm
1.45s76x slower
pnpm 11
394ms21x slower
pnpm 12
20ms1.1x slower
pnpm 12 + pnpr
20ms1.1x slower
pnpm 12 + global store
115ms6.1x slower
pnpm 12 hoisted
19ms
updateA dependency was bumped in package.json.
npm
11.7s8.8x slower
pnpm 11
6.97s5.2x slower
pnpm 12
2.29s1.7x slower
pnpm 12 + pnpr
1.33s
pnpm 12 + global store
1.81s1.4x slower
pnpm 12 hoisted
2.50s1.9x slower

Total across all scenarios

  1. pnpm 12 + pnpr16.6sfastest
  2. pnpm 12 + global store25.1s1.5x slower
  3. pnpm 1226.8s1.6x slower
  4. pnpm 12 hoisted29.2s1.8x slower
  5. pnpm 1151.9s3.1x slower
  6. npm2m 53s10x slower

All 6 scenarios added up.

Total across all scenarios with usage weights

  1. pnpm 12 + pnpr35.1sfastest
  2. pnpm 12 + global store42.7s1.2x slower
  3. pnpm 1250.7s1.4x slower
  4. pnpm 12 hoisted59.7s1.7x slower
  5. pnpm 112m 3s3.5x slower
  6. npm6m 14s11x 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.3pnpm 11v11.28.13pnpm 12v12.23.0pnpm 12 + pnprv12.23.0pnpm 12 + global storev12.23.0pnpm 12 hoistedv12.23.0
cleanA fresh clone. Nothing cached.1m 36s20.4s13.1s6.74s12.8s13.8s
lockfileCI, first install.27.3s11.1s8.59s6.42s8.70s9.22s
cacheReinstalling without a lockfile.23.6s9.87s1.61s1.07s1.18s1.79s
cache + lockfileReinstalling a project you already have.12.6s3.17s1.17s1.06s471ms1.91s
everything warmRunning install when nothing changed.1.45s394ms20ms20ms115ms19ms
updateA dependency was bumped in package.json.11.7s6.97s2.29s1.33s1.81s2.50s
Measured with npm 12.2.3 · pnpm 11 11.28.13 · pnpm 12 12.23.0 · pnpm 12 + pnpr 12.23.0 · pnpm 12 + global store 12.23.0 · pnpm 12 hoisted 12.23.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
25xfaster than nvm on “install (warm store)”
6mspnpm's best run — “run in project”
install (clean)Install Node.js 24, nothing cached.
pnpm
1.09s
fnm
2.98s2.7x slower
nvm
1.84s1.7x slower
install (warm store)Install a version you had before.
pnpm
61ms
fnm
2.95s49x slower
nvm
1.54s25x slower
run in projectRun node in a project pinned to Node.js 22.
pnpm
6ms1.2x slower
fnm
5ms
nvm
47ms9.7x slower

Total across all scenarios

  1. pnpm1.15sfastest
  2. nvm3.42s3.0x slower
  3. fnm5.94s5.1x slower

All 3 scenarios added up.

Exact numbers

Node.js Version Management — fastest run per scenario.
Scenariopnpmv12.23.0fnmv1.39.0nvmv0.41.0
install (clean)Install Node.js 24, nothing cached.1.09s2.98s1.84s
install (warm store)Install a version you had before.61ms2.95s1.54s
run in projectRun node in a project pinned to Node.js 22.6ms5ms47ms
Measured with pnpm 12.23.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.