None is when you use multiple queues  , which seems to be enabled on my 
HostedEngine VM by default.
In both cases, we shouldn't reorder  I/O requests in the VM, just to do the 
same on the Host.

That's why I left queueing to happen only on the host.

Best Regards,
Strahil NikolovOn Jan 2, 2020 07:54, Guillaume Pavese 
<[email protected]> wrote:
>
> Hi,
>
> I use something similar
> However, I think that the correct scheduler in case of virtio-scsi devices 
> (sd*) should be "noop" instead of "none"
>
> Best,
>
>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
>
> On Tue, Dec 31, 2019 at 9:27 PM Strahil <[email protected]> wrote:
>>
>> You can manually change the I/O scheduler of the disks and if that works  
>> better for you, put a rule in udev.
>>
>> Here is mine:
>>
>> [root@engine rules.d]# cat /etc/udev/rules.d/90-default-io-scheduler.rules
>> ACTION=="add|change", KERNEL=="sd*[!0-9]", ATTR{queue/scheduler}="none"
>> ACTION=="add|change", KERNEL=="vd*[!0-9]", ATTR{queue/scheduler}="none"
>>
>> [root@engine rules.d]# cat /sys/block/vda/queue/scheduler
>> [none] mq-deadline kyber
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On Dec 31, 2019 12:30, Demeter Tibor <[email protected]> wrote:
>>>
>>> Dear Users,
>>>
>>> I've successfully upgraded my 4 node hyperconverged system from 4.2.8 to 
>>> 4.3.7.
>>> After upgrade everything seems to working fine, but the whole management 
>>> system seems very slow.
>>> Spends many seconds when I clicking on "virtual machines" or I want to edit 
>>> a virtual machines. 
>>> The speed of vms and the IO is fine.
>>>
>>> It is running on a glusterfs (distributed replicate, on 3 node, 9 bricks). 
>>> There are no errors, everything fine. but terrible slow:(
>>> The engine vm has 0.2-0.3 load. 
>>>
>>> What can I do? 
>>>
>>> Thanks in advance and I wish Happy New Year!
>>>
>>> Regards,
>>> Tibor
>>>
>>>
>> _______________________________________________
>> Users mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> 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/[email protected]/message/EYHGQ6JVLHDJITYYIUXTRYFKACRZDTHT/
>
>
> Ce message et toutes les pièces jointes (ci-après le “message”) sont établis 
> à l’intention exclusive de ses destinataires et sont confidentiels. Si vous 
> recevez ce message par erreur, merci de le détruire et d’en avertir 
> immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa 
> destination, toute diffusion ou toute publication, totale ou partielle, est 
> interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer 
> l’intégrité
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/H7JKQJ4ZVSF7BLADJC43S7OTVIJ3R4PN/

Reply via email to