<div dir="ltr"><br><div class="gmail_quote">On Tue, Jun 9, 2009 at 1:44 PM, Amos Shapira <span dir="ltr"><<a href="mailto:amos.shapira@gmail.com">amos.shapira@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
We are running a cluster of web servers of various functions on top of<br>
CentOS 5, and would like to know whether and how many requests we<br>
might be dropping because of insufficient provisioning. The cluster<br>
could be hit by a a few millions requests per day soon and we'd like<br>
the stats to be there both now (in case we miss something obvious) and<br>
when the crowd comes charging.<br>
<br>
Googl'ing around for explanations of "netstat -s" and the files under<br>
/proc/net didn't come up with anything which looks like the definite<br>
answer, except maybe "packets pruned from receive queue because of<br>
socket buffer overrun", but I'm not sure what it counts.<br>
<br>
Does anyone know how to get the stats I want?<br></blockquote><div><br> </div><div>At what layer do you define "dropping a request" ? Not accepting a TCP connection (4) ? Failure to complete the request from the reverse proxy to the backend servers (HTTP error) (assuming you have backend servers - the network structure is not obvious from your original message)?<br>
<br>What answers the TCP requests to port 80?<br><br>Do you use efficient HTTP handlers already, e.g. Lighttpd or even better, nginx? :)<br><br>-- Shimi<br></div></div></div>