Closed Blasz closed 2 years ago
cc: @jonathancreamer-eb Heya, just a heads up that this affects your recent optimization in #286 . Does this look okay to you?
Yeah I'm sure for internal it probably doesn't change perf too much. Thanks for the heads up!
Released in v0.24.10
Internal dependency symlinks can become stale if the dependency changes paths in the repo so its best to always recreate them for robustness. The performance cost of this change isn't too bad as the majority of the symlinking slowdown is caused by the .bin symlinking.
Locally in atlassian-frontend this takes about 5 seconds longer but the variance between installs can be more than 5 seconds so its hard to measure the performance impact. On CI the performance was the same.
Removing the existing symlink check blows out local installs from ~30s to ~90s which verifies that the bin symlinks are the slowdowns (which makes sense as its symlinking all the bins of the entire project for each package in the repo regardless of its declared dependencies).