3 ms·
Chrome did this since the beginning but didn't use that much memory back then. So clearly processes aren't the only answer.
by ygra 13y ago
Chrome did this since the beginning but didn't use that much memory back then. So clearly processes aren't the only answer.
- kintamanimatt 13y agoChrome'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.