2 ms·
It's cool (and a bit surprising) to see that Nim was so much faster than Go, even on a toy benchmark. I wonder how Nim+httpbeast would compare against Go+fastht
by gunapologist99 3y ago
It's cool (and a bit surprising) to see that Nim was so much faster than Go, even on a toy benchmark. I wonder how Nim+httpbeast would compare against Go+fasthttp or Go+fiber on the same hardware, or also Rust and Haskell.
- BackBlast 3y agonim+httpbeast is a multi threaded library by default. Node, bun are effectively single threaded. A cursory search indicates that the go library is single threaded by default. So the nim comparison is a bit of apples and oranges. Also, the usual caveats of running micro benchmarks against localhost on an auto scaling CPU core...
- gmhafiz 3y agoIn Go's net/http library, each request is served in a new goroutine. So it uses all CPU resources by default. I'm not sure why its number is quite low though.