. And the -W
> parameter to
> allow qemu-img to write to the target out of order rather than sequential.
> This improves
> performance as the writes do not have to wait for each other to complete.
> "
>
> ----- Mail original -
> De: "aderumier"
> À:
the
> worse qemu-img will perform as compared to "rbd import".
>
>
>
> On Thu, Jul 20, 2017 at 5:07 AM, Mahesh Jambhulkar <
> mahesh.jambhul...@trilio.io> wrote:
>
>> Adding *rbd readahead disable after bytes = 0* did not help.
>>
>> [root@cephl
Adding *rbd readahead disable after bytes = 0* did not help.
[root@cephlarge mnt]# time qemu-img convert -p -O raw
/mnt/data/workload_326e8a43-a90a-4fe9-8aab-6d33bcdf5a05/
snapshot_9f0cee13-8200-4562-82ec-1fb9f234bcd8/vm_id_05e9534e-5c84-4487-9613-
1e0e227e4c1a/vm_res_id_24291e4b-93d2-47ad-80a8-
Seeing some performance issues on my ceph cluster with *qemu-img
convert *directly
writing to ceph against normal rbd import command.
*Direct data copy (without qemu-img convert) took 5 hours 43 minutes for
465GB data.*
[root@cephlarge vm_res_id_24291e4b-93d2-47ad-80a8-bf3c395319b9_vdb]# time
rb
