Yes, but the official recommendations for proxmox is still to use nocache but this is clearly only true if the images is storage on a storage with hardware raid.
Above test was done using hardware raid controller. 6disks in raid 10 with BBU.
Yes, but the official recommendations for proxmox is still to use nocache but this is clearly only true if the images is storage on a storage with hardware raid.
Obviously the recommendation needs to be adjusted then. This also follows the changes in Redhat kernels from RHEL 6.x where numerous tests and official Redhat recommendation is write-through or write-back. This is documented here: http://www.ilsistemista.net/index.p...s-on-red-hat-enterprise-linux-62.html?start=2Above test was done using hardware raid controller. 6disks in raid 10 with BBU.
if you use writethrough, you will have read cache on host, but you have already read cache in your guest buffer memory. That's why cache=none is better.Yes, but the official recommendations for proxmox is still to use nocache but this is clearly only true if the images is storage on a storage with hardware raid.
Have you read this? http://www.ilsistemista.net/index.p...s-on-red-hat-enterprise-linux-62.html?start=2if you use writethrough, you will have read cache on host, but you have already read cache in your guest buffer memory. That's why cache=none is better.
also writethrough is slower (but more secure) for write.
more info here:
http://pve.proxmox.com/wiki/Performance_Tweaks
Every performance test I have run shows that cache=none performs worst.if you use writethrough, you will have read cache on host, but you have already read cache in your guest buffer memory. That's why cache=none is better.
oK, i have done the sandra bench on 3 differents generation dell server, with pve-kernel and debian kernel, and I got exactly the same results.
So Docent,i think the problem must be related to your hardware config, maybe a different module driver version, or something like this.
I can't help you more than that, sorry .....