# Re: Nginx capping at 320 requests per second **URL:** \ **Category:** NGINX\ **Created:** [August 31, 2010, 11:20am UTC](https://www.ruby-forum.com/t/re-nginx-capping-at-320-requests-per-second/194157 "2010-08-31T11:20:46Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\ **Post date:** [August 31, 2010, 11:20am UTC](https://www.ruby-forum.com/t/re-nginx-capping-at-320-requests-per-second/194157/1 "2010-08-31T11:20:46Z")
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