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.

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-1302816780 https://github.com/facebook/react/pull/25597#issuecomment-13... Source of Bun's homepage benchmark: https://github.com/oven-sh/bun/blob/9ef33312b1b199931c29c182c4bc3984a944bb9a/bench/react-hello-world/react-hello-world.jsx#L1-L7 https://github.com/oven-sh/bun/blob/9ef33312b1b199931c29c182...