oVirt 4.2 and I/O threads configuration
Hello, in oVirt 4.1 I could enable I/O threads for a VM and then there was a field where I could define how many I/O threads (aka virtual scsi controllers from vm point of view). In 4.2 now I see only the option to enable them but not to specify the number. Next to the setting there is a symbol and a mouseover says "the field is not attached to any instance type" See this screenshot for the Edit VM -> Resource Allocation content: https://drive.google.com/file/d/1JzCiUBnWxS9fiY64_p5TJMY0uO5ZZUID/view?usp=s... Any hints for setting the number? Thanks in advance, Gianluca
Hi Gianluca, You are right, in oVirt 4.2 we removed the 'Num Of IO Threads' text field from the UI because it was decided that one IO thread is the best configuration from performance aspects for most cases (according to performance testings). We wanted to keep the UI simpler to use. So in case IO threads is enabled via Webadmin UI, only one IO thread is always created. For REST API the configuration remains unchanged in 4.2, so you can still set the number of IO threads to be >= 1 if you want for some reason. Regards, Sharon On Mon, Jun 18, 2018 at 6:21 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, in oVirt 4.1 I could enable I/O threads for a VM and then there was a field where I could define how many I/O threads (aka virtual scsi controllers from vm point of view). In 4.2 now I see only the option to enable them but not to specify the number. Next to the setting there is a symbol and a mouseover says "the field is not attached to any instance type"
See this screenshot for the Edit VM -> Resource Allocation content:
https://drive.google.com/file/d/1JzCiUBnWxS9fiY64_ p5TJMY0uO5ZZUID/view?usp=sharing
Any hints for setting the number?
Thanks in advance, Gianluca
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community- guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/ message/NJIRXBTKMBZO7HWQVUT33F6VFVKOLH5K/
On Tue, Jun 19, 2018 at 10:45 AM, Sharon Gratch <sgratch@redhat.com> wrote:
Hi Gianluca,
You are right, in oVirt 4.2 we removed the 'Num Of IO Threads' text field from the UI because it was decided that one IO thread is the best configuration from performance aspects for most cases (according to performance testings). We wanted to keep the UI simpler to use.
So in case IO threads is enabled via Webadmin UI, only one IO thread is always created.
For REST API the configuration remains unchanged in 4.2, so you can still set the number of IO threads to be >= 1 if you want for some reason.
Regards, Sharon
Thanks for confirmation. So I think the manual has to be updated. Let me know if you want me to open a documentation bug or not. Have you any suggestion on how to set from the REST API, so that I can make some tests? Have you "permission" to detail better the scenario of your test cases, landing to prefer 1 I/O thread? Gianluca
Hi, Please see my comments below. On Tue, Jun 19, 2018 at 11:51 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com
wrote:
On Tue, Jun 19, 2018 at 10:45 AM, Sharon Gratch <sgratch@redhat.com> wrote:
Hi Gianluca,
You are right, in oVirt 4.2 we removed the 'Num Of IO Threads' text field from the UI because it was decided that one IO thread is the best configuration from performance aspects for most cases (according to performance testings). We wanted to keep the UI simpler to use.
So in case IO threads is enabled via Webadmin UI, only one IO thread is always created.
For REST API the configuration remains unchanged in 4.2, so you can still set the number of IO threads to be >= 1 if you want for some reason.
Regards, Sharon
Thanks for confirmation. So I think the manual has to be updated. Let me know if you want me to open a documentation bug or not.
yes, please open a bug on that.
Have you any suggestion on how to set from the REST API, so that I can make some tests?
Sure, for setting IO threads number via REST API, you should run the following request: PUT http://engine:port/ovirt-engine/api/vms/vm-id # request body: <vm> <io> <threads>2</threads> </io> </vm> You can replace "2" by any other number, while 0 is for disabling the IO threads. Have you "permission" to detail better the scenario of your test cases,
landing to prefer 1 I/O thread?
I wasn't the one to perform those tests so I don't have those results for sending.
Gianluca
On Thu, Jun 21, 2018 at 2:43 PM, Sharon Gratch <sgratch@redhat.com> wrote:
Thanks for confirmation. So I think the manual has to be updated. Let me know if you want me to open a documentation bug or not.
yes, please open a bug on that.
There is already a bug open for the feature, follwing a case I opened for it, so I added the related comment there, also depending on what will be the decision. https://bugzilla.redhat.com/show_bug.cgi?id=1592990
Have you any suggestion on how to set from the REST API, so that I can make some tests?
Sure, for setting IO threads number via REST API, you should run the following request:
PUT http://engine:port/ovirt-engine/api/vms/vm-id
# request body: <vm> <io> <threads>2</threads> </io> </vm>
Thanks
participants (2)
-
Gianluca Cecchi -
Sharon Gratch