|
Thanks for your answer that was exactly
what I was looking for !
We'll go forward with that cache setting. ! Stephane On 13-06-11 05:24 AM, Wolfgang Hennerbichler wrote: On 06/10/2013 07:35 PM, Stephane Boisvert wrote:Hi, I wondering how safe it is to use rbd cache = truewith libvirt/qemu. I did read the documentation and it says "When the OS sends a barrier or a flush request, all dirty data is written to the OSDs. This means that using write-back caching is just as safe as using a well-behaved physical hard disk with a VM that properly sends flushes" but what does it really means.. "just as safe as physical hard drives" I don't know how safe are physical hard drives.. Is it safe to enable that setting on a prod environment ? If I don't enable that cache I'm just getting really poor write performance on the VMs.I have a working prod-environment, and I'm using it with caches, it works absolutely fine. The trick is, that the OS can send two different write requests. One is: "write, and I don't care when you finish writing, here's your data". The other one is: "write, but I want to wait until all data is on disk (sync)". Ceph Cache behaves as it should, meaning the first type of write is written when there's time for it, and the other one is written immediately.What are the implications of enabling the caching when using libvirt/qemu/kvm ?you should really upgrade to a recent qemu-version, because the qemu / rbd layer had some bugs concerning caches and high write load.Thankshope this helps Wolfgang_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com --
|
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
