topr8 - 12:49 am on Jul 6, 2012 (gmt 0)
IMHO it is nothing to do with httpd.config
it is about the databases and how well optimised they are.
also the database calls
i've seen sites that make 20+ db calls per page, it is totally un-neccesairy, the queries need to be cleaned up.
with your specs i'd put all my databases into RAM (heap files) - well maybe not all, but the most important tables that are read from all the time. i'm also a big fan of stored procedures/routines they are stored in memory too,
as Kendo says it depends what you are doing, html files without db calls or heavy processign are easy to serve,
you need to look at caching as much as you can.
i don't serve 10 million pages but i think i could.
also - consider blocking robots and scrapers - (i'm sure you do, but if you crank it up and really go hard core at blocking, you'd be amazed at how much recources you save)