Any problems with large number (160) of upstream servers (mongrels)?

Jonathan Dance jd at
Sat Nov 3 08:41:58 MSK 2007


I was trying to proxy to a large number of upstream servers (mongrels)
today and while it was working great proxying to 80 mongrels, 160
mongrels seemed to be a different matter. When running with 160, nginx
suddenly became a strange bottleneck in the system—it wasn't using
CPU, but for some reason connections would be accepted and distributed
very slowly. Putting it back down to 80 and the problem went away. All
the upstream servers are in a single upstream directive block.

I know this is vague, but as the problem occurred in a production
environment I didn't have much time to diagnose it. I am going to see
about setting a test server to see if I can figure anything out. If
you have any recommendations as to what to look at it, it would be
greatly appreciated.

Otherwise, I am mostly just wondering if anyone has seen this
before—has anyone used more upstream servers than this without a
problem? If so, is there anything special you did in your config? My
config is mostly based on Ezra's Rails config… I have 4 worker
processes, 1024 worker connections... not much else special. I am
using 0.5.26, but I don't see anything too serious in the changelog.



More information about the nginx mailing list