Hi All, I have changed my I/O scheduler to none and here are the results so far: Before (mq-deadline):Adding a disk to VM (initial creation) START: 2019-03-17 16:34:46.709Adding a disk to VM (initial creation) COMPLETED: 2019-03-17 16:45:17.996 After (none):Adding a disk to VM (initial creation) START: 2019-03-18 08:52:02.xxxAdding a disk to VM (initial creation) COMPLETED: 2019-03-18 08:52:20.xxx Of course the results are inconclusive, as I have tested only once - but I feel the engine more responsive. Best Regards,Strahil Nikolov В неделя, 17 март 2019 г., 18:30:23 ч. Гринуич+2, Strahil <hunter86_bg@yahoo.com> написа: Dear All, I have just noticed that my Hosted Engine has a strange I/O scheduler: Last login: Sun Mar 17 18:14:26 2019 from 192.168.1.43 [root@engine ~]# cat /sys/block/vda/queue/scheduler [mq-deadline] kyber none [root@engine ~]# Based on my experience anything than noop/none is useless and performance degrading for a VM. Is there any reason that we have this scheduler ? It is quite pointless to process (and delay) the I/O in the VM and then process (and again delay) on Host Level . If there is no reason to keep the deadline, I will open a bug about it. Best Regards, Strahil Nikolov Dear All, I have just noticed that my Hosted Engine has a strange I/O scheduler: Last login: Sun Mar 17 18:14:26 2019 from 192.168.1.43 [root@engine ~]# cat /sys/block/vda/queue/scheduler [mq-deadline] kyber none [root@engine ~]# Based on my experience anything than noop/none is useless and performance degrading for a VM. Is there any reason that we have this scheduler ? It is quite pointless to process (and delay) the I/O in the VM and then process (and again delay) on Host Level . If there is no reason to keep the deadline, I will open a bug about it. Best Regards, Strahil Nikolov