Go also hangs at the end with a lot of concurrent requests. I think it has something to do with how it time outs http connections.
Maybe the same thing is happening with Lua?
Also what were the specs of the computer you ran your tests on?
Maybe the same thing is happening with Lua?
Also what were the specs of the computer you ran your tests on?
I gave up micro benchmarking because once you factor in sessions and database access then everything goes in the gutter.
I've had a Go server outperform a Node server (same box, same data, same headers) by 5x when returning large amounts of json or returning large strings in general.
As soon as I had that data get returned by a database instead of hard coded strings using both language's best drivers for that database then the reqs/s evened out, in fact Node ended up performing slightly better for both latency and reqs/s.
The other (possible) option for real world use is to tweak nf_conntrack_tcp_timeout_time_wait and nf_conntrack_tcp_timeout_established to flush done connections from connection tracking quicker.
Have had some good use with this - read more here: http://blog.engineyard.com/2012/linux-scalability
The tests were made on a Micro VPS from Afterburst.com (which I own), on an empty/not-yet-deployed node.