Don't know anything about typo, but an alternative to throwing more hardware at it could be to optimize your site. My story (redis/mongodb) peaked at the same

Don't know anything about typo, but an alternative to throwing more hardware at it could be to optimize your site. My story (redis/mongodb) peaked at the same time as yours, and my linode 1024 ($40/m), which also houses about 7 different projects, didn't go past 5% cpu usage. Going with Disqus lets you outsource the only dynamic part of your blog post. This lets you set a long cache header, or at least to serve it from cached memory. Even if you don't outsource your comments, I bet caching the page for 2-3 minutes in memory would solve most of your problems. Also, cache headers on your other assets wouldn't hurt. Nor would moving away from Apache. Sounds like a good weekend project :)