Throttle Disk IO
CompletedWe 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
-
Official comment
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 -
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.
-
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.
Please sign in to leave a comment.
Comments
14 comments