So I run multiple sites on this server and plan to keep adding more, so that's another reason configuration maintenance is an issue. Not to mention one day I plan to write a web gui to handle all this configuration ... and I don't need nginx's super-duper performance. I need a stable piece of software to configure, apache does everything, I've been using it for years, know all the ins and outs, and memory is cheap. Just mod_php is the bear and you add drupal to that and you have a beast.
I don't know what the bottleneck is really, that is part of the problem. But I know that every now and then when we we get bursts of traffic I can find with a /server-status that 50 apache processing are in a write state.
Then again you have the same problem with things like drupal, that just plop media all over the place and it's up to the client to maintain the separation of media in their code. Drupal users don't do that.
I think you do know what the problem is ;-)
What is your PHP Error handling and logging set to? How big are your Apache access_log and error_log files?
Cheers
If so, there are a number of approaches to take. If your app is blocking on sending/receiving data to/from the client, it would benefit you to segregate the actual app servers from the frontend servers. You can use mod_fastcgi and run your PHP stuff in FastCGI, or you can use a frontend threaded apache talking to a backend PHP apache via mod_proxy.
If you are blocking on things like database access or other non-web IO, then you need an event loop so your app can do something else while waiting for IO. I don't know what your options are in the PHP world, but this is very easy to do in Perl.
Finally, real threads will probably also solve your problem. I recommend CL or Haskell. (Although I think Slicehost still uses an ancient Xen that can't handle SBCL. Oops.)