Replies: 3 comments 6 replies
-
Wow, you just saved me. This simple fix reduced my install time from 10min to less than 1min lol. You are awesome - thank you! |
Beta Was this translation helpful? Give feedback.
1 reply
-
This is really unfortunate. If hard links are so inefficient on Windows then should we recommend using copying? Is it getting slow when there are more than a given number of hard links to the same file? |
Beta Was this translation helpful? Give feedback.
5 replies
-
I am also somewhat confused by this issue. The current known information is as follows:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After using pnpm for a while, it's become unbearably slow.
#7133
In this issue @zkochan mentioned, "pnpm is too slow is too broad","But with this title and description the issue just attracts people with different unrelated issues".After seeing this, I decided to delete all the
node_modules
directories installed via pnpm, as well as the.pnpm-store
, and then ranGet-ChildItem -Recurse | Where-Object {$_.LinkType -eq 'HardLink'}
in Windows PowerShell to ensure all pnpm hard links were cleaned up.I saw a discussion that offered a great method, and I would recommend doing it like this:
https://github.com/orgs/pnpm/discussions/4413
The execution speed improved significantly afterwards. For example, with the store,
pnpm install
used to take over 30 minutes, but now, without the store, the firstpnpm install
only takes 6 minutes.In this case, the slow speed was due to the impact of hard links. After a clean removal, the speed returned to normal.
Hopefully, this method will be helpful.
Beta Was this translation helpful? Give feedback.
All reactions