As an unplanned follow up to my previous post I wanted to reply to some of the feedback I received and take another run at this little IO test. The feedback was generally around â€œwhatâ€ I tested rather than the â€œwhyâ€ and â€œhowâ€. I had no doubt the â€œwhyâ€ was super clear and I was not interested in debating the â€œhowâ€ because as I said before this is a very informal test so I am glad I did not receive either of those remarks. As for the â€œwhatâ€ feedback it boiled down as:
- You get what you pay for â€“ at $9 a month for Azure and free for EC2 what did you expect?
- Try testing on a more realistic platform, one that someone may actually expect decent IO.
- How about a newer â€œCloud Readyâ€ OS bro?
- Hey buddy, we are friends and I work for Rackspace, so why didnâ€™t you include them in the mix?
All are fair comments â€“ so lets take another stab at this and see what paying a bit more money can get us.
For those that did not read the previous post, the reason I am doing this testing is because the general feeling from a few of us using VMs running in the cloud is the IO seems or feels pretty slow. While Amazon, Windows Azure, and RS give you options when it comes to the number CPUs, network speed, disk space, and RAM it seems when it comes to disk IO you get what you get. While Amazon EC2 does give you designators such as â€œlowâ€ or â€œhighâ€ IO for some of their instances, there is no real indication of what that actually means or how it compares to other providers.