undefined | Better HN

0 pointsygra12y ago0 comments

Chrome did this since the beginning but didn't use that much memory back then. So clearly processes aren't the only answer.

0 comments

1 comments · 1 top-level

kintamanimatt12y ago

Chrome's codebase also got more complex so now every new process consumes a lot more memory. It's a way of achieving concurrency, but it's not necessarily the best way in terms of memory footprint.

j / k navigate · click thread line to collapse