Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-14 Thread Alexandre DERUMIER
ve.proxmox.com Envoyé: Vendredi 14 Septembre 2012 09:42:29 Objet: Re: [pve-devel] qcow2 bench and speed optimisations xfs : ok http://en.wikipedia.org/wiki/XFS#Sparse_files ext4:ok ext3:ok ext2:ok http://superuser.com/questions/218395/about-file-size-and-disk-usage-in-ext3 zfs: ok

Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-14 Thread Alexandre DERUMIER
DERUMIER" Cc: pve-devel@pve.proxmox.com Envoyé: Vendredi 14 Septembre 2012 09:17:09 Objet: RE: [pve-devel] qcow2 bench and speed optimisations > so raw and qcow2 with metadatas alloc are sparse files, but you need a > filesystem which support it. Do you know a filesystem whi

Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-14 Thread Dietmar Maurer
> so raw and qcow2 with metadatas alloc are sparse files, but you need a > filesystem which support it. Do you know a filesystem which does not support sparse files? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mail

Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-14 Thread Alexandre DERUMIER
th lvm too :) - Mail original - De: "Dietmar Maurer" À: "Alexandre DERUMIER" Cc: pve-devel@pve.proxmox.com Envoyé: Vendredi 14 Septembre 2012 07:58:42 Objet: RE: [pve-devel] qcow2 bench and speed optimisations > >>If so, we can do that by default, becaus

Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-13 Thread Alexandre DERUMIER
xandre DERUMIER" Cc: pve-devel@pve.proxmox.com Envoyé: Vendredi 14 Septembre 2012 07:58:42 Objet: RE: [pve-devel] qcow2 bench and speed optimisations > >>If so, we can do that by default, because metadata is small (128MB/TB). > Note that the size file is the full size of the d

Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-13 Thread Dietmar Maurer
> >>If so, we can do that by default, because metadata is small (128MB/TB). > Note that the size file is the full size of the disk (no sparse file). That is bad. What performance to you get when you pre-allocate the raw file? ___ pve-devel mailing list

Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-13 Thread Alexandre DERUMIER
- Mail original - De: "Dietmar Maurer" À: "Alexandre DERUMIER" , pve-devel@pve.proxmox.com Envoyé: Vendredi 14 Septembre 2012 07:10:42 Objet: RE: [pve-devel] qcow2 bench and speed optimisations > 4)qemu-img create -f qcow2 -o > size=100,prealloc

Re: [pve-devel] qcow2 bench and speed optimisations

2012-09-13 Thread Dietmar Maurer
> 4)qemu-img create -f qcow2 -o > size=100,preallocation=metadata,compat=1.1,lazy_refcounts=on > file.img > So I think it should be great to add an option for preallocatting metadatas, > the boost is really huge. Above command only pre-allocates metadata, so creation is still fast? If so,

[pve-devel] qcow2 bench and speed optimisations

2012-09-13 Thread Alexandre DERUMIER
Hi, I'm playing with qcow2 on my new netapp pnfs cluster,some optimisations can be done. some benchmarks : 1).raw file : 2io/s 2).qcow2 file, sparse : 300 io/s :/ 3).qcow2, preallocated metadatas (nosparse): 4000io/s 4).qcow2, with lazy counts + preallocated metadatas : 4000io/s. (lazy