Hacker News Reader

The RAM usage is from JavaScript heaps, not from multiple copies of the binaries.

(There basically aren't memory metrics that can show the effect of binary sizes on macOS. It'd show up as disk reads/page ins/general slowdowns instead, but SSDs are so fast that it's very hard to see one.)

View on HN

Multiple copies of the same binary can't share a memory page for the code. They do take more RAM.

And there are no metrics you can look at to see the impact of this, so it's not contributing to any of the metrics you are seeing, as I said.

Reply on news.ycombinator.com