C++ vs Node.js HTTP benchmark with wrk: Crow 5.4k req/s, Node http 12k, uWebSockets 57k. Same route, same laptop, with code and why Crow lost to Node.
1 comment
There are always benchmarks where the one or the other might be faster; this is the reason why we use benchmark suites and geometric means of the factors to make the comparison more representative.
In the above results, Node.js was twice as fast as C++ in the Storage benchmark, and equally fast in Richards and CD, but overall C++ was twice as fast.
Implementations can differ significantly, which you confirmed with the two C++ implementations you measured. The Are-we-fast-yet suite includes guidelines (see https://github.com/smarr/are-we-fast-yet/blob/master/docs/gu...) for this purpose which must be followed by new implementations, and which assure comparability.
Read the full thread on Hacker News →
Related stories
- Hacker News · 127 points · about 10 hours ago
- Hacker News · 1 points · 3 days ago
- Why Your Production API Needs Idempotency Keys (And How to Build an Engine in Node.js & Redis)dev.toDEV Community · 5 points · 11 days ago
- Hacker News · 1 points · 4 days ago
- Lobsters · 1 points · almost 12 years ago
- Hacker News · 5 points · 2 days ago