We are currently running Nginx as a front end LB to a single PHP App Server. When we need a bit more horse power, I can divert traffic to the LB itself to process PHP requests with a minor change in the config.<br><br>We are serving close to 2mm page views a day and growing. The Nginx configuration is a dual core, dual CPU AMD processor system, 32 bit with 8GB of RAM. We are also using it for delivery of static assets (everything except PHP). The CPU utilization on the box at peak is below 3% and nginx processing 3000+ connections at any given time.<br>
<br>I also configured the PHP app server as a Nginx server and it serves as a backup in case the primary nginx server fails.<br><br>I'm very happy with the confguration, adding another PHP app server will be a breeze, although session management is going to be difficult.<br>
<br><div class="gmail_quote">On Tue, Sep 15, 2009 at 4:16 PM, Gena Makhomed <span dir="ltr"><<a href="mailto:gmm@csdoc.com">gmm@csdoc.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;">
On Tuesday, September 15, 2009 at 18:19:38, David Murphy wrote:<br>
<br>
DM> Not sure if this is possible ( as I haven't tried it)<br>
DM> but what about building nginx on Damn Small Linux and having<br>
DM> a boot cd or ramdisk, or even boot flash. You could literally take<br>
DM> something like a PowerEdge 1425 or so and have a kicking minimalistic<br>
DM> LB hardware running on nginx.<br>
<br>
DSL - Desktop OS, linux distro for i486 with 2.4.x linux kernel,<br>
optimized for minimal RAM usage and old computers.<br>
no linux 2.6.x kernel - means no "epoll" at all.<br>
<br>
therefore - DSL is totally useless for high traffic load balancer as base OS.<br>
<br>
DM> Technically if you were so inclined, you could even write DSL and nginx<br>
DM> to a prom chip so its 100% automated, I'm better if nginx does everything<br>
DM> you need it would be a lot cheaper than the hardware normal route with the<br>
DM> same if not better stability.<br>
<br>
question was not about most cheaper "solution", but about "high traffic LB".<br>
<br>
DM> Personally what I would do is (assuming you have ESX), run 2 VM's both<br>
DM> running nginx on dedicated NICs. Then one your switching set up an<br>
DM> active/active fail over to those nice ( and have the VM's on separate ESX<br>
DM> hosts).<br>
<br>
DM> You would then have a fully redundant LB system so if nginx on one node<br>
DM> crashes the fail over would route all traffic to the other LB.<br>
<br>
if, for example, crashes mainboard of esx server with these VM's -<br>
both VM's go down. so, this is not "a fully redundant LB system".<br>
<br>
hardware of ESX server is "single point of failure".<br>
<br>
--<br>
Best regards,<br>
<font color="#888888"> Gena<br>
<br>
<br>
</font></blockquote></div><br>