3 ms·
Depends heavily on how you have configured Apache. If you are using something like PHP and the forking model (most common MPM configuration), you can only handl
by jamescun 12y ago
Depends heavily on how you have configured Apache. If you are using something like PHP and the forking model (most common MPM configuration), you can only handle as many requests as you have workers; additionally you are spinning up a full PHP interpreter when serving static assets. In my experience[1], putting Nginx in front of Apache to serve static assets and leaving Apache as a sort of application server is one of the lowest hanging fruit in scaling a LAMP application.
[1] Was Co-Founder/CTO of a medium-sized PHP PaaS company
- Supermighty 12y agoThis was how we did it at my last job, a state university.
- stevekemp 12y agoI'd agree, but I suspect that anybody who cares about PHP-performance has probably already moved to FPM.
- y0ghur7_xxx 12y ago> additionally you are spinning up a full PHP interpreter when serving static assets. I think that if you do this you are one RewriteRule away from doing it right. > In my experience[1], putting Nginx in front of Apache to serve static assets and leaving Apache as a sort of application server I also think that using nginx only for static content is wasting perfectly good resources for nothing. Apache can serve static assets just as good as nginx does. No need for an other layer in your stack.