[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt-users] qcow2 performance

cache=default would set the cache to writethrough.
Also to improve perfomance, you could try virtio based disks.


Thanks and Regards
Saurav Lahiri
Hexagrid Computing

--- On Mon, 6/2/12, Stefan G. Weichinger <lists xunil at> wrote:

From: Stefan G. Weichinger <lists xunil at>
Subject: Re: [libvirt-users] qcow2 performance
To: "SAURAV LAHIRI" <saurav_lahiri yahoo com>
Cc: libvirt-users redhat com
Date: Monday, 6 February, 2012, 9:50

Am 06.02.2012 09:59, schrieb SAURAV LAHIRI:
> Hello,
> The cache settings would also depend on the underlying storage. If you
> are planning to use something like ext4 partition on the local harddisk
> then cache=none would be suitable.

Right now we try that, yes.

As mentioned in the other msg I am currently not able to use cache=none,
VM doesn't start that way ... still looking ...

For now, yes, qcow2 on ext4.

> It would be good to avoid cache=writeback on production environment as
> there no guarantees that the write actually got saved to harddisk.
> cache=writethrough though slower than writeback is the most recommended
> for the production environments.

Right now I run "cache=default" ... what would that mean? (aio=threads

> To get better performance it would be good to identify what additional
> performance can be extracted from the underlying storage subsystem.

Right now it looks more like the communication between the application
and the client PCs is the bottleneck.

Copying files from the VM over LAN is fast! So I assume I/O isn't the
problem anymore. As mentioned I also chose "deadline"-scheduler for
IO-scheduling on the host.

We just try to check through everything to be able to nail it down on
the software house delivering that application ...

Thanks, Stefan

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]