Deno vs. Bun performance is rigged
unetworkingab.medium.com
Deno vs. Bun performance is rigged
1–10 of 196 posts
Re: Deno vs. Bun performance is rigged
#2Why isn’t bun utilising multiple cores?
Re: Deno vs. Bun performance is rigged
#3Post and heading are written to attribute this to malice, without offering any proof. It seems likely given how new Bun is that the benchmark writers simply lacked familiarity.
Re: Deno vs. Bun performance is rigged
#4[deleted]
Re: Deno vs. Bun performance is rigged
#5Im surprised performance at this level even matters to most folks. Like if you truly thought this microbenchmark was the reason to choose one runtime over another Id be shocked. It makes it equally surprising that this error from the Deno crew, who should all know better.
In either case, I hope they announce a correction and move on to more important matters. If youre trying to shave another tiny bit of rps out of your boxes then thats an incredible success problem; not the kind 99.999 of companies will need.
Re: Deno vs. Bun performance is rigged
#6It seems like there is some battle between the two with an article bashing Bun's performance metrics by a Deno contributor just the other day. The article doesn't do nearly as good of a job pointing out the differences though and the allegations by the Deno contributor which appear to be legitimate.
Also, just because Bun is single threaded doesn't mean they should get special exceptions in performance testing. If they don't like the numbers then give a comparable test with Bun using multithreading.
Re: Deno vs. Bun performance is rigged
#7Im surprised performance at this level even matters to most folks. Like if you truly thought this microbenchmark was the reason to choose one runtime over another Id be shocked. It makes it equally surprising that this error from the Deno crew, who should all know better. In either case, I hope they announce a correction and move on to more important matters. If youre trying to shave another tiny bit of rps out of yo…
Javascript is plagued with idea that it is slow while it is not. Many devs now have PTSR after arguing day after day that javascript is a good thing and not slow.
Performance is a very important thing in js world for a peace of mind of devs.
Re: Deno vs. Bun performance is rigged
#8Why isn’t bun utilising multiple cores?
I can’t find the tweet right now but I follow the developer on twitter and his rationale was essentially that he wanted to focus on nailing single core speeds before expanding to multi core.
I assume this has to do with how extremely experimental bun is at the moment anyway. So they are focusing on nailing the fundamentals before attempting anything that would make it „production ready“ such as multi core support.
Re: Deno vs. Bun performance is rigged
#9This post doesn’t link to the original benchmark, or any code to verify what’s being suggested. Along with the click-bate heading, I think it’s fairly irrelevant.
My assumption is that this is a micro benchmark doing just an echo response, that is so far from what Bun/Deno/Node will ever be used for it’s just a farce.
The speed of your application frameworks http server will (almost) never be your bottleneck.
Developer experience, available libs, security model, packaging, deployment story, and to some extent resource usage (within reason) are far more important.
Re: Deno vs. Bun performance is rigged
#10Im surprised performance at this level even matters to most folks. Like if you truly thought this microbenchmark was the reason to choose one runtime over another Id be shocked. It makes it equally surprising that this error from the Deno crew, who should all know better. In either case, I hope they announce a correction and move on to more important matters. If youre trying to shave another tiny bit of rps out of yo…
Exactly. Very few companies will need to reach 1000 reqs/s consistently, let alone 100k reqs/s.
StackOverflow peaks at about 6000 reqs/s and it's an extremely popular website.