salfers opened a new issue, #8384:
URL: https://github.com/apache/cloudstack/issues/8384
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
KVM hypervisor
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18 or latest
~~~
##### SUMMARY
<!-- Explain the problem/feature briefly -->
The [qemu
documentation](https://github.com/qemu/qemu/blob/master/docs/throttle.txt#L142)
explains why this is important:
> When applying IOPS limits all I/O operations are treated equally
regardless of their size. This means that the user can take advantage
of this in order to circumvent the limits and submit one huge I/O
request instead of several smaller ones.
>
> QEMU provides a setting called throttling.iops-size to prevent this
from happening. This setting specifies the size (in bytes) of an I/O
request for accounting purposes. Larger requests will be counted
proportionally to this size.
In libvirt this option is called `size_iops_sec` inside the `<iotune>`
section ([ref](https://libvirt.org/formatdomain.html)).
Other big clouds such as AWS also use this mechanism to fairly allocate IOPS.
##### STEPS TO REPRODUCE
Checking the CloudStack code shows that this option is currently not
supported:
https://github.com/apache/cloudstack/blob/1411da1a22bc6aa26634f3038475e3d5fbbcd6bb/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java#L1173C14-L1207
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
