News for hackers. Stuff that matters.
Re:Deno vs. Bun performance is rigged by detaro on Sunday October 16, 2022 @10:24AM (#33223818)
And a real-world deployment of a single-threaded interpreter just runs multiple instances of it, so do and compare that. No need to "handicap" anything.
Re:Deno vs. Bun performance is rigged by zamalek on Sunday October 16, 2022 @10:34AM (#33223890)
My gut would say that you're paying 2x the overhead for a JS runtime. Of course, such a benchmark (edit: N instances of Bun and N instances of Deno) would be much more realistic/relevant.
Re:Deno vs. Bun performance is rigged by m00x on Sunday October 16, 2022 @11:31AM (#33224349)
But then you need twice the initial app memory. This can be substantial for larger apps.

There are definitely benefits of using multiple cores at once on a single app.

Re:Deno vs. Bun performance is rigged by detaro on Sunday October 16, 2022 @12:28PM (#33224863)
Sure. not an excuse to not benchmark it that way - if it struggles due to memory it'll show up after all.
Re:Deno vs. Bun performance is rigged by simpsond on Sunday October 16, 2022 @12:43PM (#33225014)
Copy on write fork mitigates some of that.
Re:Deno vs. Bun performance is rigged by squeaky-clean on Sunday October 16, 2022 @01:30PM (#33225430)
There was a recent post about a new Ruby server implementation. The author pointed out that for interpreted languages, forking quickly deviates and gains very little benefit from copy-on-write. However! Pre-warming the first instance and then forking afterwards brought the memory savings back down to compiled levels. No real point to my comment except that it was new knowledge to me, and that efficiency of forking really depends on the implementation of what/when you're forking.
Re:Deno vs. Bun performance is rigged by m00x on Sunday October 23, 2022 @03:41AM (#33305306)
It's not clear what OP is saying. I assumed multiple container instances, but even then, CoW isn't as efficient.