@nim_lang just did a quick (& stupidly simple) benchmark comparing asyncHttpServer with a plain @nodejs http server. The #Nodejs server seems ~3.5x faster than the #nim one... I did expect opposite results! Am I doing something stupid or is this expected? 
After setting up the @nim_lang "-d:release" flag and changing the @nodejs implementation to use the cluster module, these are some new results.
@nim_lang is winning (as expected) but just slightly (62k vs 51k req/sec). Again, this is a silly benchmark, but nonetheless a good proof of @nodejs raw performance with async workflows!
Hey @nim_lang, is there any way (and maybe an example) on how to respond using content-encoding chunked and avoid to send the "content-length" header? I spent a couple of hours on this today but I wasn't able to figure out a decent solution for it :(
• • •
Missing some Tweet in this thread? You can try to
force a refresh
