This is a point I always have trouble impressing on people.   They do a simple benchmarks on a tiny code base that pulls some data from the database, spits out some data, and they compare and PHP seems to be lightning fast.<p>The problem is that because it's interpreted at some point PHP slows down in proportion to the <i>size of your code base</i>.   A small app runs really fast, a big app with 100,000 lines of code will kill your server unless you modularize it really really well - which harder than it seems, because the more modularized you make it the more separate "includes" you end up with in different files and then you come to realize that including a lot of files itself is a problem.   And the nature of PHP's very loose coupling tends to lead to code that is nearly impossible to do large scale refactoring on once you have gone too far down the path.<p>I work on an application that has a very thin PHP layer that performs some simple web services that are the back end for a pure Java web app.  Amazingly, when we load test it, the PHP part is the bottleneck, burning CPU like crazy just parsing all our files ... over ... and over ... and over.   The java code meanwhile, while theoretically doing far more "work", is completely bored.   We will probably look at using an accelerator of some kind or maybe just rewriting all the PHP in another language.