Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

May be I'm missing something but at a glance new SSD-based m3.medium EC2 instance doesn't provide any disk performance advantage. I didn't run benchmark tools yet, but directory copying, directory deleting, and hdparm don't show any difference between system and SSD volumes - /dev/sda1 and /dev/sdb. Am I wrong? Or there is some special configs?

TIA, Vitaly

share|improve this question

closed as off-topic by Rex, ceejayoz, Ward, TheCleaner, mdpc Feb 27 '14 at 1:10

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must demonstrate a minimal understanding of the problem being solved. Try including attempted solutions, why they didn't work, and the expected results. See How can I ask better questions on Server Fault? for further guidance." – Rex, ceejayoz, Ward, TheCleaner
If this question can be reworded to fit the rules in the help center, please edit the question.

the /dev/sda or /dev/xvda device continues on top of EBS volumes, SSD are only available as Ephemeral Storage.

When create your instance, select /dev/sdb as Instance Store 0 under storage session.

share|improve this answer
fgbreel, thank you! I launched SSD instance via AWS portal, based on existing AMI image. I don't remember that I had an option to select "/dev/sdb as Instance Store 0", but i'll review it again. Is there a way to see type of storage into instance properties under AWS portal? – Vitaly Feb 25 '14 at 4:37

You can run iostat to check the performance. First create a big file where /dev/xvdb or /dev/sdb is mounted on (write)

cd /mnt/sdb
dd if=/dev/zero of=filename bs=1 count=100000000 seek=1048575 

Then run (read):

cat filename

Then install iostat (Ubuntu):

sudo apt-get install sysstat

This is the output on an m3.medium after running the iostat command:

root@ip-10-113-150-143:/mnt# iostat
Linux 3.2.0-54-virtual (ip-10-113-150-143)  02/25/2014  _x86_64_    (1 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           0.77    0.03    4.24    0.29    3.56   91.11

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
xvdap1            1.10        17.45        11.07     237589     150688
xvdb              0.28         0.14         8.45       1917     115108


As you can see the performance on xvdb is slightly higher than in xvdap1 (sda) for writes (so you may be right) Where you really see the improvement is in reads. 17.45 kB_read/s.

Hope this helps.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.