An avg of 240 dbIO/s is entirely different from peak time IO/s. When someone like Jeff Atwood posts a link using their service, they could easily see 10x the vo

An avg of 240 dbIO/s is entirely different from peak time IO/s. When someone like Jeff Atwood posts a link using their service, they could easily see 10x the volume. Volume might be really stagnant for 45 minutes, then bam, 10 percent of their req's for the hour come in within a 2-3 minute span. Judging by their blog-post, I'm assuming they needed to have the infrastructure to handle that kinda load. Either way, I modded you up for a pretty thorough analysis (and because I largely agree with you (it basically is a mapped 301 Location: http://newsite/) http://newsite/)). From my armchair standpoint(1), a 256 mb slice + Redis + nginx should be able to handle 10x the volume easy. (1) Well not quite armchair, a good 30 percent of my firm's business is directly related to scaling.