Re:Nginx has replaced Apache as the most used web server amo...
by mgkimsal on Monday May 26, 2014 @09:03AM
(#7799563)
wouldn't just changing the apache keep alive have been even easier than setting up a whole other web server and adding that to the mix?
If the nginx keep alive was set at 15 seconds, you'd have had a similar problem, no?
Re:Nginx has replaced Apache as the most used web server amo...
by seunosewa on Monday May 26, 2014 @09:15AM
(#7799601)
No. Because Nginx doesn't dedicate a thread or process to each open connection.
Re:Nginx has replaced Apache as the most used web server amo...
by jebblue on Monday May 26, 2014 @09:54AM
(#7799725)
Doesn't that raise security concerns?
Re:Nginx has replaced Apache as the most used web server amo...
by marcosdumay on Monday May 26, 2014 @10:33AM
(#7799828)
Yes, it requires a sandbox for things like PHP.
But it's limited to it. Most other web stacks come with their own sandbox. And Apache also puts PHP in a sandbox for unrelated issues.
The app was doing polling every 10 seconds and apache had a 15 seconds keep alive. So each user of the app was maintaining an apache process alive.
Disabling the keep-alive was not acceptable, so I just threw nginx in front to do the keep-alive, memory usage was immediately reduced by ~75%.
If I knew apache better I might have been able to do it with just apache, but nginx is so simple to use...