Verify latest release

• I verified that the issue exists in the latest pnpm release

pnpm version

v9.1.3

Which area(s) of pnpm are affected? (leave empty if unsure)

CLI

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

use two runners
small runner:

"cpu": "2",
"memory": "5Gi"

and a large runner:

"cpu": "15",
"memory": "25Gi"

make sure to cache the pnpm store and have the restored global store.
now when running pnpm install --frozen-lockfile or pnpm install --frozen-lockfile --prefer-offline compare the final time that it took for pnpm to move/link the packages from global store to node_modules.

Describe the Bug

in our case we have two linux/arm64 runners with the exact same specs mentioned in the Reproduction steps.
We have a cache hit on our pnpm store and the store is restored. When running the command.
on the smaller runner:

on the larger runner:

there is a significant difference. between the times.

Expected Behavior

Expected behaviour is to see closer times for both runs.

Which Node.js version are you using?

20.15.1

Which operating systems have you used?

• macOS
• Windows
• Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

Debian