The fact of the matter is that the small instances from Linode and Media Temple could not perform the tests as conducted with their out of box configurations. I made no enhancements to any platform. Some helpful readers have pointed out some settings I can change that will allow the benchmarks to complete successfully so I am going to do a follow-up post with all of these "tweaks" implemented across all the providers. I am being as objective as possible here, don't let the fact that I work for Rackspace fog the air.
These tests are also very easy to duplicate on your own if you really want to test the data set and results.
-Chad
If you don't want us to recognize this as the cheap PR-piece it is then perhaps next time refrain from conclusions like the following (verbatim quote):
The tests show some significant performance benefits when running on the Rackspace Cloud Servers platform most likely due to (in my opinion) a more robust network infrastructure, lower hardware utilization, and better host server hardware.
And from unverified claims like (quote):
Even if different web server software is used, it is unlikely that the results and trends would differ.
Otherwise, if that truly was supposed to be a honest benchmark then please hand in your engineer-badge at the door...
Requests per second: 5162.92 [#/sec] (mean)
Time per request: 24.792 [ms] (mean)
Time per request: 0.194 [ms] (mean, across all concurrent requests)
100% 60 (longest request)
I think he's comparing this to a Rackspace 1GB, which is actually cheaper than EC2's small instance; the more direct comparison is to the Rackspace 2GB.
You m1 large is $0.34 per hour, vs $0.06 per hour on the Rackspace machine in the blog (I believe). You only got twice as many request per second out of it, so on the requests per second per dollar metric (the real metric, I think), ec2 is lagging.