amazon ec2amazon-web-servicesperformance
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
(moved from the question itself to a separate answer instead)
According to a user on HN (a KVM developer?) this is due to small packet performance in Xen and also KVM. It's a known problem with virtualization and according to him, VMWare's ESX handles this much better. He also noted that KVM are bringing some new features designed alleviate this (original post).
This info is a bit discouraging if it's correct. Either way, I'll try the steps below until some Xen guru comes along with a definitive answer :)
Iain Kay from the xen-users mailing list compiled this graph:
Notice the TCP_CRR bars, compare "2.6.18-239.9.1.el5" vs "2.6.39 (with Xen 4.1.0)".
Submit this issue to a Xen-specific mailing list and the xensource's bugzilla as suggested by syneticon-dj
A message was posted to the xen-user list, awaiting reply.
Create a simple pathological, application-level test case and publish it.
A test server with instructions have been created and published to GitHub. With this you should be able to see a more real-world use-case compared to netperf.
Try a 32-bit PV Xen guest instance, as 64-bit might be causing more overhead in Xen. Someone mentioned this on HN. Did not make a difference.
Try enabling net.ipv4.tcp_syncookies in sysctl.conf as suggested by abofh on HN. This apparently might improve performance since the handshake would occur in the kernel. I had no luck with this.
Increase the backlog from 1024 to something much higher, also suggested by abofh on HN. This could also help since guest could potentially accept() more connections during it's execution slice given by dom0 (the host).
Double-check that conntrack is disabled on all machines as it can halve the accept rate (suggested by deubeulyou). Yes, it was disabled in all tests.
Check for "listen queue overflow and syncache buckets overflow in netstat -s" (suggested by mike_esspe on HN).
Split the interrupt handling among multiple cores (RPS/RFS I tried enabling earlier are supposed to do this, but could be worth trying again). Suggested by adamt at HN.
Turning off TCP segmentation offload and scatter/gather acceleration as suggested by Matt Bailey. (Not possible on EC2 or similar VPS hosts)
Terminated instances will go away after a few hours. There is nothing you can do to manually remove them.
Not to worry, you won't get billed for it.
Best Answer
the
/dev/sdaor/dev/xvdadevice continues on top of EBS volumes, SSD are only available as Ephemeral Storage.When create your instance, select
/dev/sdbasInstance Store 0under storage session.