So, after my previous post where I used bonnie++ to benchmark my desktop machine, I decided to benchmark the I/O performance of the virtual server (or as Amazon like to call it, an “instance”) with the same tool.
So, what can we tell from these numbers? How do they compare with my desktop SATA hard drive? Here are the same numbers from the SATA drive:
Well, we can see that when it comes to the Sequential Output numbers, the local SATA wins in all three of the numbers and the CPU utilization is exactly the same on both of the systems. It’s the same story for the Sequential Input numbers, although there doesn’t seem to be as much of a difference as with the Sequential Output numbers.
In the Random Seeks, the AWS machine blows away the local SATA drive, both in terms of Random seeks per second and the latency numbers. The only place where it loses out is in consuming much more CPU than the local system.
In the Sequential Create category, AWS also comes out on top, although, for some reason I wasn’t able to get Read and Delete numbers for the local disk.
The Random Create category is pretty much even, with neither system really standing out.
So, there you have it, the AWS infrastructure isn’t as bad as I had originally thought. Also, one thing to keep in mind is that the type of EC2 instance tested was just the basic “free” instance which Amazon provides. I would expect that better provisioned instances would perform even better when it comes to the same test.