16 messages in ru.sysoev.nginxRe: Surviving Digg?
FromSent OnAttachments
Neil ShethApr 29, 2008 1:37 pm 
Aleksandar LazicApr 29, 2008 2:07 pm 
Rt IbmerApr 29, 2008 2:26 pm 
Neil ShethApr 29, 2008 4:00 pm 
Neil ShethApr 29, 2008 4:11 pm 
Rt IbmerApr 29, 2008 5:05 pm 
Igor SysoevApr 30, 2008 12:08 am 
Sasa UgrenovicApr 30, 2008 2:24 am 
Aleksandar LazicMay 1, 2008 1:24 pm 
Neil ShethMay 1, 2008 5:08 pm 
Aleksandar LazicMay 3, 2008 2:16 am 
Neil ShethMay 5, 2008 7:39 pm 
Grzegorz NosekMay 5, 2008 11:54 pm 
Rt IbmerMay 6, 2008 5:48 am 
Aleksandar LazicMay 6, 2008 9:39 am 
eliottMay 6, 2008 10:26 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Surviving Digg?Actions...
From:Rt Ibmer (rtib@public.gmane.org)
Date:Apr 29, 2008 5:05:05 pm
List:ru.sysoev.nginx

Ok, tried that, no notice printed out. What is a good value for worker_connections?

http://wiki.codemongers.com/NginxMainModule#worker_processes talks about these
settings.

proxy_connect_timeout 90; proxy_send_timeout 90; proxy_read_timeout 90;

Are these reasonable?

Depends on what is normal for your app. IMO these are WAY to high for defaults.
It means that nginx will wait 1.5 minutes(!) for a downed server to respond
before moving to your other box. You should also look at max_fails and
fail_timeout.

Yup, just trying to figure out what exactly it is that we need! We've hit the front page of digg before, though not as big last time.

To me it seems nginx did its job. Glad you solved the FDs with ulimit -n that is
the only obvious thing that jumps out at me on the nginx side. I highly suspect
an application bottleneck from what you describe, such as a slow db or
something.

Thanks for the help!

My pleasure. I am just a few weeks into nginx and this list so it feels good to
help out and be in a position to start giving back. HTH.