[Galaco]

> Faster than your local environment. Builds complete up to 20% faster and package installs complete >= 5x faster than yarn/npm.

Above is a quote from the post. I feel like this is a stupid question, but how can running yarn/npm in a browser on my machine be faster than running yarn/npm on my machine? Particularly when each page load runs a fresh npm/yarn install?

Nonetheless, this is a incredible piece of software that i'll be following closely

[giorgioz]

I've also asked myself this question. I think the comparison is not with a local environment but rather with running node/yarn/npm on a remote virtual machine/ci. This is my hypothesis, I have no proof that's what they meant.

[dspillett]

I'm wondering if there is more happening in-memory, even if the project files and modules themselves are on-disk (accessed via FileSystemAPI) the vscode/node/other bits including temporary files may be held in RAM once initially loaded and never swapped out.

If that is the reason, then if your machine becomes memory constrained, the performance will drop through the floor quicker than with full-local installs.

It could be a mix of this and your suggestion (lower network latency related bottlenecks than experienced with non-local deployment).

[altano]

I was wondering the same thing

[grassthehopper]

I'm also curious about this