[virt-tools-list] Default use of caching on raw volumes
Nikolai K. Bochev
n.bochev at grandstarco.com
Tue Aug 17 13:17:46 UTC 2010
Well i just tried this ( i never really did read the documents on that part ) and amazingly my loadavg on the kvm host dropped by a factor of 10.
All the load was coming out of a heavily loaded VM with pgsql in it that was writing all the time ( zabbix monitoring etc. ).
I guess this should really be set as default, not sure if it's up to virt-manager or libvirt.
From: "Jamin W. Collins" <jcollins at asgardsrealm.net>
To: virt-tools-list at redhat.com
Sent: Saturday, August 14, 2010 1:16:51 AM
Subject: [virt-tools-list] Default use of caching on raw volumes
If possible I'd like to get some opinions on the following bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=623188
Obviously, I believe that virt-manager should be defaulting to disabling
caching for disks backed by raw volumes as qemu suggests. There is a
huge performance difference in doing so. AFAIK, there is no difference,
in terms of risk, between no cache and Writethrough.
I don't quite get Daniel's response and subsequent closing the bug
report indicating that it's a policy decision for virt-manager and the
like. I filed the report where virt-manager's web site indicated the
report should be filed.
_______________________________________________
virt-tools-list mailing list
virt-tools-list at redhat.com
https://www.redhat.com/mailman/listinfo/virt-tools-list
--
Nikolai K. Bochev
System Administrator
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20100817/bc47949e/attachment.htm>
More information about the virt-tools-list
mailing list