News for hackers. Stuff that matters.
Re:Nginx vs Apache performance by jedberg on Monday March 16, 2009 @11:14PM (#519319)
We just use an http load balancer (haproxy) and have the app servers talk http directly. No need for a web server, which makes things much more stable. We use nginx for static content though (haproxy points at nginx for the static content).
Re:Nginx vs Apache performance by catch23 on Tuesday March 17, 2009 @07:56AM (#519747)
I've found that nginx still performs around 10-15% better than haproxy. I was using the stable version of haproxy, so they may have improved speed with the experimental versions. One nice thing about nginx is that it can use local unix sockets instead of ports for load balancing. The downside of nginx is that you'll have to compile your own -- most Linux distros come with an ancient version of nginx that actually is buggy in certain ways.
Re:Nginx vs Apache performance by jedberg on Tuesday March 17, 2009 @12:10PM (#520036)
Yeah, the new version of haproxy has been shown to be able to hold up on a 10Gbps connection with no problems. We're using 1.3.15.2 with a couple of patches from the experimental version.
Re:Nginx vs Apache performance by catch23 on Tuesday March 17, 2009 @08:45PM (#520907)
well holding up the 10Gbps connection isn't the problem really, i don't think it manages the balance pool as effectively as nginx. I don't believe haproxy supports unix domain socket balancing either.
Re:Nginx vs Apache performance by smallpaul on Tuesday March 17, 2009 @01:53AM (#519481)
How do you do process management? Do you have a static or dynamic number of app server processes/threads?
Re:Nginx vs Apache performance by jedberg on Tuesday March 17, 2009 @12:15PM (#520048)
Process management is done with a custom tool. In theory we could have a dynamic number of apps, but in practice it is static. Occasionally we have to take a few out of rotation, and haproxy handles it just fine.