News for hackers. Stuff that matters.
Re:Go as an alternative to Node.js for Very Fast Servers by danieldk on Saturday February 23, 2013 @01:46AM (#5268812)
Because this isn't the same benchmark, did you compile with -O2? The Go version allocates a 1MB slice once and sends it to every user. The Haskell version literally states that it should make a bytestring during every request. The compiler might optimize it away with the right flags.
Re:Go as an alternative to Node.js for Very Fast Servers by danieldk on Saturday February 23, 2013 @02:40AM (#5268906)
I tried the benchmark as in the article, and the above Haskell compiled with '-O2'. With Go I usually get around 1320 reqs/second, with Snap around 1100. Both using four threads.

With a single-threaded Warp instance, I could get around 1350 reqs/seconds, though it failed dramatically when I used more threads.

Re:Go as an alternative to Node.js for Very Fast Servers by e12e on Saturday February 23, 2013 @09:40AM (#5269729)
No, I didn't (see my other comment). I expect (especially Haskell) to be correct without -O2 -- being slower isn't a problem - crashing - not so much.

Tried it now -- both haskell versions crash with -O2 as well (and ab -n 100000 -c 1000 -- so not the same benchmark as the original -- and a rather silly test).