You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am planning to dive in deeper to see if I can improve the speed of my monorepo, and maybe I could create a PR of a timing reporter.
It's been a while since I looked into the install algorithm so not sure exactly what would already be possible by piping --reporter ndjson. With async steps/tasks, usually it can be complicated to add timing.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a very large monorepo and I would like more insight into how long each stage is taking and why, during
pnpm add
andpnpm install
commands.Sometimes adding a package is quick, other times it takes much longer, and seems like it scans all the dependencies.
A common thing is seeing it take 1 second per 1000 packages it checks if they are
reused
.I am planning to dive in deeper to see if I can improve the speed of my monorepo, and maybe I could create a PR of a timing reporter.
It's been a while since I looked into the install algorithm so not sure exactly what would already be possible by piping
--reporter ndjson
. With async steps/tasks, usually it can be complicated to add timing.Inline messages or summary after command completes (similar to https://github.com/stephencookdev/speed-measure-webpack-plugin for Webpack).
Is there existing instrumentation code for different steps/phases/tasks?
How far would
--reporter=ndjson
get us I wonder?Related
https://discord.com/channels/731599538665553971/731599538665553975/831221571519512657
Beta Was this translation helpful? Give feedback.
All reactions