[pve-devel] Improve the I/O in PVE
Cesar Peschiera
brain at click.com.py
Thu Jun 12 12:15:36 CEST 2014
Correct Dietmar
But i am saying that if the images of the VMs are in a file system and not in a partition LVM of block of disks, may be that change the "io=native" to "io=threads" give us more speed access of disk in input/output
And as in mode native "PVE" use a file system as storage, may be convenient that pve-manager see if the image of the VM is in a file system or is in a partition of blocks of disks (that is possible with a VG of LVM partition), and depending of this condition, what IO should use pve-manager to raise KVM and gain more speed of access disk
But as I have not tried it yet, I can not confirm that this change will be appropriate.
----- Original Message -----
From: Dietmar Maurer
To: Cesar Peschiera ; pve-devel at pve.proxmox.com
Sent: Wednesday, June 11, 2014 2:37 PM
Subject: RE: [pve-devel] Improve the I/O in PVE
AFAIK we already use native aio
From: pve-devel [mailto:pve-devel-bounces at pve.proxmox.com] On Behalf Of Cesar Peschiera
Sent: Mittwoch, 11. Juni 2014 19:40
To: pve-devel at pve.proxmox.com
Subject: [pve-devel] Improve the I/O in PVE
Hello
In this link i see how improve the I/O in PVE when a image of disk is used, may be that will be better to do changes in the next release of pve-manager
I don't have tested, but may be that someone can do it?
io=native => for block device based VMs.
io=threads => for file-based VMs.
http://www.sebastien-han.fr/blog/2013/08/12/openstack-unexplained-high-cpu-load-on-compute-nodes/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20140612/fef4b153/attachment.htm>
More information about the pve-devel
mailing list