Contact Us

support@onapp.com

U.S: (+1) 888-876-8666

UK: +44 (0) 203-318-5364

Throttle Disk IO

Completed
Follow
Avatar
David Majchrzak

We need a way to throttle Disk IO per vdisk or VM.

This should preferably be done in the virtualization layer so that it applies to all storage solutions.

QEMU/KVM has come quite far in the last few years.

References:

http://wiki.qemu.org/ChangeLog/1.1#Block_devices

http://wiki.qemu.org/Features/DiskIOLimits

https://fedoraproject.org/wiki/QA:Testcase_Virtualization_IO_Throttling

http://libvirt.org/formatdomain.html#elementsDisks

 

 

31

Comments

14 comments

Sort by Date Votes
  • Official comment
    Avatar
    Raymond Paxton

    This feature has been implemented in OnApp version 5.4.  You are now able to set limits for all virtual disks inside a datastore and on an individual virtual disk level.  Please see the following link for further information:

     

    https://docs.onapp.com/display/54AG/Edit+Data+Store+IO+Limits

     

    Comment actions Permalink
  • Avatar
    Filipe Santos

    is very important when we sell IOPs limit.

     

    0
    Comment actions Permalink
  • Avatar
    WEIFENG DING

    I need this feature too. The high IO on one VM could cause the IS storagenode hung which cause multiple vms have IO error.

    0
    Comment actions Permalink
  • Avatar
    Lupu Pitkanen

    This feature would essential and I'm quite surprised not to see it implemented yet.

    There could be for example two values to be set for a data store:

    • Maximum IOPS for a disk created on a particular data store (for example 300 IOPS for a FC data store and 5000 IOPS for a SSD data store)
    • Maximum IO bandwidth for a disk created on a particular data store (for example 50 MB/s for a FC data store and 300 MB/s for a SSD data store)

    Alternatively/additionally the IOPS and bandwidth limit values could be set on a virtual disk basis and could be billable resources just like Port Speed is at the moment.

    0
    Comment actions Permalink
  • Avatar
    Shaun McGuane

    We really need this feature too.... any update from onapp on this?

    0
    Comment actions Permalink
  • Avatar
    Dominik Nowacki

    Definitely useful! +1

    0
    Comment actions Permalink
  • Avatar
    Nick Fawbert

    +1 from me

    IO management is absolutely critical imho - the ability for one guest to DOS other systems within the cloud is something you wouldn't expect from a cloud.

    0
    Comment actions Permalink
  • Avatar
    Cerrie Russell

    +1 As QEMU can already do this and also virtio I think? 

     

     

    0
    Comment actions Permalink
  • Avatar
    innofield

    +1 Thank you!

    0
    Comment actions Permalink
  • Avatar
    Bojan Jovanovic

    +1 We really need this feature too. Any progress in the meantime?

    Thanks, Bojan

    0
    Comment actions Permalink
  • Avatar
    info

    +1... Currently VM's are able to utilize 100% the storage block. Which can cause IO load issues and CPU loads. This setup is totally unwanted I would think. Sadly OnApp focusses more on new product development and not on getting its core product proper. 

    0
    Comment actions Permalink
  • Avatar
    info

    Hi,

    As this request is out for over two years, the Onapp comunity or at least we from Serveo, would like to have an official statement by Onapp regarding this feature and when it will be added to Onapp.

    Currently all VM's are able to MAX IOPS the storage. E.g. with minimal 10 mb/s and the base of 8kb combined with random writings this can cause an internal to slow down any storage / creating IO wait. As it is even part of Qemu, and implementation like this could be done overnight. http://wiki.qemu.org/Features/DiskIOLimits/Requirements

     

    Waiting on your reply. 

    1
    Comment actions Permalink
  • Avatar
    Raymond Paxton

    The ability to set IOP limits on vDisk is planned and we will update when there is further news.

    1
    Comment actions Permalink
  • Avatar
    Rabi Hanna

    Raymond,

     

    any news? it's been 4 months now, and there are at least 3 new onapp versions released, this is really required if you have a lot of VM's.

    0
    Comment actions Permalink

Please sign in to leave a comment.