I've been using Drupal for a while now and have had to use some duct tape style hacks to get things working well. One of them was using file caches for specific high-volume pages that aren't modified often and then redirecting those pages via htaccess. For example, I have a page of applications, with a url alias of example.com/applications. This is a heavily used page that is only modified once every few weeks. So, I pull the page as an anonymous user and save it in a cache directory on the server as applications.html. Then within .htacess, I redirect it to this file using the following:
RewriteRule ^applications$ http://example.com/cache/applications.html [L]
This reduced the load on the server quite a bit. It's still struggling badly under load, but it's better. The main reason I had to do this is that I have lots of users (15,000+) and most of them are logged in all the time... making the Drupal cache mostly useless with them. But, this got me thinking... wouldn't it make sense to be able to set specific pages within a Drupal site to treat ALL users as anonymous, thus being able to better utilize Drupal's cache? Or, perhaps, all users except those of a specific type (say 'admin' users)?
I know editing would be an issue (how would Drupal display the Edit tab?)... so just showing it for specific types of users would work. Any thoughts on this?