undefined | Better HN

0 pointsculi3y ago0 comments

Those benchmarks may not actually hold up to independent analysis:

https://medium.com/deno-the-complete-reference/node-js-vs-de...

0 comments

2 comments · 1 top-level

Jarred3y ago· 1 in thread

Two things about the linked benchmark:

1) That benchmark appears to be bottlenecked by the HTTP client — that’s why the numbers are so close for each runtime. Effectively, it is benchmarking the http client and not the http server.

The benchmarking tool has to be at least as fast the server and it needs to support HTTP keep alive. That means popular Node.js-based benchmarking tools like autocannon don’t produce useful results in benchmarks like these

Instead, a tool like oha or wrk or bombardier is better

2) That benchmark is not using the ReactDOM server build for Bun's runtime, which is used in Bun's benchmark and is part of the next release of react-dom.

PR: https://github.com/facebook/react/pull/25597#issuecomment-13...

Source of Bun's homepage benchmark: https://github.com/oven-sh/bun/blob/9ef33312b1b199931c29c182...

culiOP3y ago

Thanks for the response. If you haven't already, I'd hit up the author as they've done and continue to regularly do similar benchmarks

j / k navigate · click thread line to collapse