Hard to say.. I am not personally familiar with Tornado but I do know nginx with a very similar config with keepalive's at 5/10 seconds will do much more than that..

It's a very odd situation. I know it sounds dumb but do you have any errors in your 'dmesg' or in the nginx logs? Is it running out of buffered memory or system sockets?

Is reuse connections on in your sysctl's? I would double-check your sysctl config and personally I would run KeepAlive. This would ensure reusing connections and not opening a new connection for every request.

Everyone has their own opinion keepalive with attacks, large volumes of traffic, etc. However, we have found it to perform much better, less resources, and worse case - if you are having a bottleneck from something else then it would likely be more efficient.

-Kevin
------Original Message------
From: dpn
To: nginx@nginx.org
ReplyTo: nginx@nginx.org
Subject: Re: Nginx capping at 320 requests per second
Sent: Aug 31, 2010 1:19 AM

Hello again, we added another machine with 15 workers and are still
getting the 320rps cap from nginx:
http://dl.dropbox.com/u/367355/nginxday.png

I've posted my config earlier... I don't suppose anyone has a suggestion
about what might be causing the issue?

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,123754,125474#msg-125474


_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx