yes, I know enginx coule handle many many connections(for example, 30000), and I know how engix do it with static files. It's amazing !<br><br>my quest is:<br><br>if every request needs to get dynamic conetent(not static file, image, css ...), nginx has to proxy the request to backend apache server. in this circumstance, if all apache server process have been occupied, then following requests have to wait until a apache server is released. right ?<br>
<br>if we have 200 apache process and all backend apache server are occupied, the other 29800 requests have to wait untile a apache process is freed or socket connection timeout?<br><br>"The main nginx advantage is that it gets quickly whole response from backend<br>
and frees it to handle other requests."<br><br>Sorry, I don't understand how enginx could "get quickly whole response", the response time is decided by apache server(business logic), why enginx could do it more quickly than direct connetion ? <br>
<br>3ks<br><br>---Xuepeng<br> <br><br><div class="gmail_quote">2009/8/10 Igor Sysoev <span dir="ltr"><<a href="mailto:is@rambler-co.ru">is@rambler-co.ru</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, Aug 10, 2009 at 05:00:05PM +0800, Xuepeng Li wrote:<br>
<br>
> if it's is 1:1 module and nginx establishes HTTP 1.0 only to apache<br>
> server, every time enginx receive a request, it has to proxy the request to<br>
> apache server, what is the advantange make enginx as reverse proxy other<br>
> than make direct connection between browser and apache?<br>
<br>
</div>The main nginx advantage is that it gets quickly whole response from backend<br>
and frees it to handle other requests. If your responses are small, then<br>
nginx will be just useless overhead.<br>
<div class="im"><br>
> 2009/8/10 Joshua Zhu <<a href="mailto:zhuzhaoyuan@gmail.com">zhuzhaoyuan@gmail.com</a>><br>
><br>
> > Hi,<br>
> ><br>
</div>> > 2009/8/10 ????????? <<a href="http://xuepeng.li" target="_blank">xuepeng.li</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>>:<br>
<div class="im">> > > So, it means that client (browser) will get a 5** error ?<br>
> > > if this, what's the meaning of enginx high concurrent connection ?<br>
> > ><br>
> > > 2009/8/10 Weibin Yao <<a href="mailto:nbubingo@gmail.com">nbubingo@gmail.com</a>><br>
> > >><br>
</div><div><div></div><div class="h5">> > >> ????????? at 2009-8-10 10:37 wrote:<br>
> > >>><br>
> > >>> hi all<br>
> > >>> i have a question that how nginx handle connection with backend web<br>
> > >>> server ?<br>
> > >>> for example, i have a nginx server for receiving client request, and<br>
> > >>> reverse proxy to backend 2 web server(such as apache server), every<br>
> > apache<br>
> > >>> server have 100 child process(prefork module). so, if there are 1000<br>
> > client<br>
> > >>> requests, how nginx map 1000 requests to only 200 apache server<br>
> > process?<br>
> > >>><br>
> > >> Nginx can handle more than 10000 concurrent connections, but apache with<br>
> > >> prefork's max concurrent connections is the number of its process<br>
> > number. So<br>
> > >> Apache will send the 5** error.<br>
> > >><br>
> > >> --<br>
> > >> Weibin Yao<br>
> > >><br>
> ><br>
> > It's 1:1 model actually and for now nginx establishes HTTP 1.0<br>
> > connections only.<br>
> ><br>
> > In your circumstance, you use nginx as a reverse proxy, hence it's not<br>
> > nginx but your upstream's duty to handle real connections, I.E., your<br>
> > upstream's capacity must be big enough, otherwise, it will become the<br>
> > bottleneck.<br>
> ><br>
> > Cheers!<br>
> ><br>
> > --<br>
> > Joshua Zhu<br>
> ><br>
> ><br>
<br>
</div></div><font color="#888888">--<br>
Igor Sysoev<br>
<a href="http://sysoev.ru/en/" target="_blank">http://sysoev.ru/en/</a><br>
<br>
</font></blockquote></div><br>