[ovirt-users] Gluster - performance.strict-o-direct and other performance tuning in different storage backends

Hello Everyone, As per some previous posts, this "performance.strict-o-direct=on" setting caused trouble or poor vm iops. I've noticed that this option is still part of default setup or automatically configured with "Optimize for virt. store" button. In the end... is this setting a good or a bad practice for setting the vm storage volume ? Does it depends ( like maybe other gluster performance options ) on the storage backend: - raid type / jbod - raid controller cache size I am usually using jbod disks attached to lsi hba card ( no cache ). Any gluster recommendations regarding this setup ? Is there any documentation for best practices on configurating ovirt's gluster for different types of storage backends ? Thank you very much ! Have a great week, Leo -- Best regards, Leo David