Post your VPS iops

Comments

• wrox Member

  February 2013 edited February 2013

  Here's some results from my TorqHost Xen container.

  root:~# ioping -c 10 .
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=1 time=0.2 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=2 time=0.3 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=3 time=0.3 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=4 time=0.3 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=5 time=0.2 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=6 time=0.3 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=7 time=0.2 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=8 time=0.2 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=9 time=0.2 ms
  4096 bytes from . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f): request=10 time=0.3 ms
  
  --- . (ext3 /dev/disk/by-uuid/a9b8cb71-a5d7-4617-83ed-56222f96ee8f) ioping statistics ---
  10 requests completed in 9004.6 ms, 3900 iops, 15.2 mb/s
  min/avg/max/mdev = 0.2/0.3/0.3/0.0 ms
  
• hostingwizard_net Member

  March 2013

  iops is one measure among many but it matters. It's part of the responsiveness of the VPS. High iops and low iowait mean a smoother running, and as such, often a stabler one. I finally made that column public.
• xBytez Member

  March 2013

  NodeDeploy:

  10 requests completed in 9005.9 ms, 2384 iops, 9.3 mb/s
• yomero Member

  March 2013

  @hostingwizard_net said: I finally made that column public.

  HOLY COW!
  70k from FitVPS????
• black Member

  March 2013

  76k iops....
  
• kornnflake Member

  March 2013 edited March 2013

  FrontRangeHosting KVM-384D

  10 requests completed in 9107.4 ms, 96 iops, 0.4 mb/s
  min/avg/max/mdev = 0.6/10.4/22.8/8.1 ms
  

  Could be better
• Damian Member

  March 2013

  I thought we determined that ioping results didn't seem to correlate to anything and weren't really trustable?
• kornnflake Member

  March 2013 edited March 2013

  @Jack said: @kornnflake that on IDE or virtio?

  was on IDE But it's still kinda slow using virtio:

  10 requests completed in 9019.7 ms, 594 iops, 2.3 mb/s
  min/avg/max/mdev = 0.3/1.7/12.2/3.5 ms
  

  Ran a few tests, this is about the average. @Corney can you please take a look into this? I'm on Node Breck, thanks!
• black Member

  March 2013

  @Damian said: I thought we determined that ioping results didn't seem to correlate to anything and weren't really trustable?

  Personally, I noticed a correlation between iops and VPS responsiveness. Though after 7k iops and up, they all seem the same (to a human). However, to a machine, I'm sure it'll still noticeable.
• DalComp Member

  March 2013

  @kornnflake said: Ran a few tests, this is about the average. @Corney can you please take a look into this? I'm on Node Breck, thanks!

  @FRCorey
• sleddog Member

  March 2013

  After much testing my conclusion is that ioping doesn't in any way reflect real-world performance. I have several awesome VMs that have be delivering excellent service for months -- in some cases years -- on which ioping shows poor results.

  It's another of those benchmarking tools where a good result may be good, but a poor result is not necessarily bad
• xBytez Member

  March 2013

  @xBytez said: NodeDeploy:

  10 requests completed in 9005.9 ms, 2384 iops, 9.3 mb/s

  Sorry this was IDE ._.

  This is VirtIO:

  4096 bytes from / (ext4 /dev/vda3): request=1 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=2 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=3 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=4 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=5 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=6 time=0.0 ms
  4096 bytes from / (ext4 /dev/vda3): request=7 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=8 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=9 time=0.2 ms
  4096 bytes from / (ext4 /dev/vda3): request=10 time=0.2 ms

  --- / (ext4 /dev/vda3) ioping statistics ---
  10 requests completed in 9004.3 ms, 5149 iops, 20.1 mb/s
  min/avg/max/mdev = 0.0/0.2/0.2/0.1 ms
• snelweg Member

  March 2013 edited March 2013

  Shovehost

  10 requests completed in 10824.1 ms, 5 iops, 0.0 mb/s
  min/avg/max/mdev = 0.2/182.3/865.9/332.4 ms

  it is really really slow......

  update: I canceled after comparing to other LET vps's I have. The supportstaff can be rude and arrogant.
• 24khost Member

  March 2013

  @Shovehost ooh oooh!!!! ^^^^^^
• BradND Member

  March 2013

  @xBytez much better ;-)
• budingyun Member

  March 2013

  @Shovehost

  @snelweg said: 10 requests completed in 10824.1 ms, 5 iops, 0.0 mb/s

  min/avg/max/mdev = 0.2/182.3/865.9/332.4 ms

  Epic iops is epic.
• xBytez Member

  March 2013

  Amazon AWS:

  ioping -c 10
  request=1 time=0.0 ms
  request=2 time=0.0 ms
  request=3 time=0.0 ms
  request=4 time=0.0 ms
  request=5 time=0.0 ms
  request=6 time=0.0 ms
  request=7 time=0.0 ms
  request=8 time=0.0 ms
  request=9 time=0.0 ms
  request=10 time=0.0 ms

  10 requests completed in 9085.2 ms, 48309 iops, 188.7 mb/s