mirror of
https://github.com/pnpm/pnpm.git
synced 2026-07-17 11:12:25 -04:00
51839cd3b8
The cold batch in `CreateVirtualStore` ran each per-snapshot `InstallPackageBySnapshot` as a future inside one cooperative `try_join_all` task, and each future called the *blocking* `CreateVirtualDirBySnapshot::run` (a `rayon::join` over CAS import + symlink layout) directly. Because all the futures share a single task, a blocking call in one prevents the others from being polled — so the 1308 slot-link operations on a fresh install serialized one-at-a-time, each paying its own `rayon::join` dispatch. The warm batch already avoids this by linking every slot in a single `rayon` `par_iter`. This was invisible on warm/restore installs (everything goes through the warm batch) but dominated the cold path: a pnpr client install, whose fast offloaded resolution routes every package through the cold batch, spent ~14.5s in `CreateVirtualStore` where an equivalent local fresh install — which pre-fills the store during its slower resolution and so hits the warm batch — spent ~5-7s linking. Defer the slot link out of the per-snapshot download future (new `InstallPackageBySnapshot::defer_link`) and run all the cold links in one parallel `rayon` pass after the downloads, mirroring the warm batch. On a fresh ~1300-package install through a pnpr server this cut `CreateVirtualStore` from ~14.5s to ~9.5s and the end-to-end install from ~18.5s to ~13s — now faster than the equivalent non-pnpr install (~15.5s), which it should be since the pnpr client offloads resolution and downloads less metadata. The progress events are unchanged in kind and order (`fetched`/`found_in_store` still fire during download, `imported` still fires once the slot is linked). --- Written by an agent (Claude Code, claude-opus-4-8).
简体中文 | 日本語 | 한국어 | Italiano | Português Brasileiro
Fast, disk space efficient package manager:
- Fast. Up to 2x faster than the alternatives (see benchmark).
- Efficient. Files inside
node_modulesare linked from a single content-addressable storage. - Great for monorepos.
- Strict. A package can access only dependencies that are specified in its
package.json. - Deterministic. Has a lockfile called
pnpm-lock.yaml. - Works as a Node.js version manager. See pnpm runtime.
- Works everywhere. Supports Windows, Linux, and macOS.
- Battle-tested. Used in production by teams of all sizes since 2016.
- See the full feature comparison with npm and Yarn.
To quote the Rush team:
Microsoft uses pnpm in Rush repos with hundreds of projects and hundreds of PRs per day, and we’ve found it to be very fast and reliable.
Platinum Sponsors
|
Gold Sponsors
|
|
|
|
|
|
|
|
Silver Sponsors
|
|
|
|
|
|
|
⏱️ Time.now |
Support this project by becoming a sponsor.
Background
pnpm uses a content-addressable filesystem to store all files from all module directories on a disk. When using npm, if you have 100 projects using lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be stored in a content-addressable storage, so:
- If you depend on different versions of lodash, only the files that differ are added to the store.
If lodash has 100 files, and a new version has a change only in one of those files,
pnpm updatewill only add 1 new file to the storage. - All the files are saved in a single place on the disk. When packages are installed, their files are linked from that single place consuming no additional disk space. Linking is performed using either hard-links or reflinks (copy-on-write).
As a result, you save gigabytes of space on your disk and you have a lot faster installations!
If you'd like more details about the unique node_modules structure that pnpm creates and
why it works fine with the Node.js ecosystem, read this small article: Flat node_modules is not the only way.
💖 Like this project? Let people know with a tweet
Getting Started
Benchmark
pnpm is up to 2x faster than npm and Yarn classic. See all benchmarks here.
Benchmarks on an app with lots of dependencies:
License
MIT, except the pnpr/ directory, which is source-available under the PolyForm Shield License 1.0.0.