3 ms·

I'm not saying you're wrong, but I'm having trouble squaring this analysis with Chrome's notoriously high memory usage compared to Safari. What's gunking up Chr

I'm not saying you're wrong, but I'm having trouble squaring this analysis with Chrome's notoriously high memory usage compared to Safari. What's gunking up Chrome if not V8's memory needs?

hajile 4y ago
The bulk of the browser's memory usage is the rendering engine and surrounding stuff rather than the JS on the page. v8 has a compacting GC[0] while JSC does not[1]. This was the result of the v8 team taking out a bunch of time to write a new GC that was released in 2018 (Orinoco). Here's a comparison of a simple job. With lots of concurrency, Bun is 20-30% faster, but uses 60% more memory. https://medium.com/deno-the-complete-reference/hello-world-performance-bun-vs-node-js-2c9d383b94c1 https://medium.com/deno-the-complete-reference/hello-world-p... Here's a little about JSC, Hermes, and v8 memory in React Native. https://medium.com/walmartglobaltech/react-native-memory-profiling-jsc-vs-v8-vs-hermes-1626949a653b https://medium.com/walmartglobaltech/react-native-memory-pro... [0] https://v8.dev/blog/trash-talk https://v8.dev/blog/trash-talk [1] https://webkit.org/blog/12967/understanding-gc-in-jsc-from-scratch/ https://webkit.org/blog/12967/understanding-gc-in-jsc-from-s...
- Jarred 4y ago
  > Here's a comparison of a simple job. With lots of concurrency, Bun is 20-30% faster, but uses 60% more memory. That benchmark is out of date. In Bun v0.3, memory usage in situations like that dropped by 4x - https://bun.sh/blog/bun-v0.3.0 https://bun.sh/blog/bun-v0.3.0, meaning it uses around half as much memory as Node. Prior to Bun v0.3, Bun wasn't scheduling the garbage collector in conjunction with the event loop and that led to memory not being reclaimed correctly on idle
  - culi 4y ago
    This comparison uses Bun v0.4 and still often finds Deno ahead https://medium.com/deno-the-complete-reference/node-js-vs-deno-vs-bun-server-side-rendering-performance-comparison-f80a5abc766f https://medium.com/deno-the-complete-reference/node-js-vs-de...

I'm not saying you're wrong, but I'm having trouble squaring this analysis with Chrome's notoriously high memory usage compared to Safari. What's gunking up Chrome if not V8's memory needs?

hajile 4y ago

The bulk of the browser's memory usage is the rendering engine and surrounding stuff rather than the JS on the page. v8 has a compacting GC[0] while JSC does not[1]. This was the result of the v8 team taking out a bunch of time to write a new GC that was released in 2018 (Orinoco). Here's a comparison of a simple job. With lots of concurrency, Bun is 20-30% faster, but uses 60% more memory. https://medium.com/deno-the-complete-reference/hello-world-performance-bun-vs-node-js-2c9d383b94c1 https://medium.com/deno-the-complete-reference/hello-world-p... Here's a little about JSC, Hermes, and v8 memory in React Native. https://medium.com/walmartglobaltech/react-native-memory-profiling-jsc-vs-v8-vs-hermes-1626949a653b https://medium.com/walmartglobaltech/react-native-memory-pro... [0] https://v8.dev/blog/trash-talk https://v8.dev/blog/trash-talk [1] https://webkit.org/blog/12967/understanding-gc-in-jsc-from-scratch/ https://webkit.org/blog/12967/understanding-gc-in-jsc-from-s...

Jarred 4y ago
> Here's a comparison of a simple job. With lots of concurrency, Bun is 20-30% faster, but uses 60% more memory. That benchmark is out of date. In Bun v0.3, memory usage in situations like that dropped by 4x - https://bun.sh/blog/bun-v0.3.0 https://bun.sh/blog/bun-v0.3.0, meaning it uses around half as much memory as Node. Prior to Bun v0.3, Bun wasn't scheduling the garbage collector in conjunction with the event loop and that led to memory not being reclaimed correctly on idle
- culi 4y ago
  This comparison uses Bun v0.4 and still often finds Deno ahead https://medium.com/deno-the-complete-reference/node-js-vs-deno-vs-bun-server-side-rendering-performance-comparison-f80a5abc766f https://medium.com/deno-the-complete-reference/node-js-vs-de...