On 1/17/2017 1:51 AM, Daniel P. Berrange wrote:
Also note the io setting is only relevant for file/block device
backed disks. ie if using the in-QEMU network client for RBD,
Gluster, iSCSI, NFS, etc thenm the io setting has no effect at
all so can be ignored.
Ahh, that is important. We most
On Mon, Jan 16, 2017 at 10:52:08AM -0800, W Kern wrote:
> Googling provides lots of interesting info on the use of these in various
> situations such as SSD, number of VMs in the pool etc.
>
> What is the default in Libvirt (or is the default 'neither')
Libvirt has no default policy - it just del
Googling provides lots of interesting info on the use of these in
various situations such as SSD, number of VMs in the pool etc.
What is the default in Libvirt (or is the default 'neither')
Sincerely
W Kern
___
libvirt-users mailing list
libvirt-use
Hello,
Regarding KVM - in particular RHEL 6.1 x86_64:
I just did a set of benchmarks comparing the effect of
versus
Using Oracle's "orion" tool with an XIV backend, I got:
With io='native':
Maximum Large MBPS=964.41
Maximum Small IOPS=11797
Minimum Small Latency=7.57
WithOUT io='native':
Ma
