Re: [ovirt-users] slow performance with export storage on glusterfs

On Mon, Nov 20, 2017 at 5:22 PM Jiří Sléžka <jiri.slezka(a)slu.cz&gt; wrote: gluster storage operations are using fuse mount - so every write: - travel to the kernel - travel back to the gluster fuse helper process - travel to all 3 replicas - replication is done on client side - return to kernel when all writes succeeded - return to caller So gluster will never set any speed record. Additionally, you are copying from raw lv on FC - qemu-img cannot do anything smart and avoid copying unused clusters. Instead if copies gigabytes of zeros from FC. However 7.5-10 MiB/s sounds too slow. I would try to test with dd - how much time it takes to copy the same image from FC to your gluster storage? dd if=/rhev/data-center/2ff6d0ee-a10b-473d-b77c-be9149945f5f/ff3cd56a-1005-4426-8137-8f422c0b47c1/images/ba42cbcc-c068-4df8-af3d-00f2077b1e27/c57acd5f-d6cf-48cc-ad0c-4a7d979c0c1e of=/rhev/data-center/mnt/glusterSD/10.20.30.41:_rhv__export/81094499-a392-4ea2-b081-7c6288fbb636/__test__ bs=8M oflag=direct status=progress If dd can do this faster, please ask on qemu-discuss mailing list: https://lists.nongnu.org/mailman/listinfo/qemu-discuss If both give similar results, I think asking in gluster mailing list about this can help. Maybe your gluster setup can be optimized. Nir