From: "Christian MICHON" <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QCow v2
Date: Tue, 11 Jul 2006 13:30:18 +0200 [thread overview]
Message-ID: <46d6db660607110430w74fa175avc0f01a52bb91f44a@mail.gmail.com> (raw)
In-Reply-To: <47604893-CBC5-4EF2-B048-00DA701301A3@claunia.com>
ok, I did this experiment (long and painful).
a XP2003/SP1 qemu guest required 964,231,168 bytes qcow image.
zlib qcow image became 459,686,368 bytes.
lzma estimation (4k clusters) is 437,038,838 bytes.
Yes, 5% are still gained, but the time to get the lzma'ed qcow is
disastrous (especially on systems with anti-virus and anti-malware).
Do you still think it's worth it ?
On 7/4/06, Natalia Portillo <claunia@claunia.com> wrote:
> Just there is a question:
>
> If improvement is 5%, IS NOT THE SAME with a 5Mb HDD that with a 5Gb
> HDD.
>
> Wanna do testing with more real scenarios?
>
> Like a Windows XP full installation for example?
>
> I'm very sure that there will be a real difference.
>
> Regards
>
> El 04/07/2006, a las 15:51, Christian MICHON escribió:
>
> > for what it's worth:
> > qcow with "lzo -9" would become 4155352 bytes (bigger than original
> > zlib qcow).
> >
> > yet it's true at the compression and decompression stages that it
> > feels faster...
> >
> > On 7/4/06, Elefterios Stamatogiannakis <estama@dblab.ece.ntua.gr>
> > wrote:
> >> I agree
> >>
> >> Lzma and zlib are pretty much equivalent, so there is pretty much
> >> nothing to be gained except slightly more compression.
> >>
> >> On the other hand with lzo (1) there would be quite a considerable
> >> speed
> >> improvement at the cost of compression.
> >>
> >> It could also mean that reading on the qcow format could some
> >> times be
> >> faster (with compressible data) than reading directly from the
> >> hard disk.
> >>
> >> lefteris
> >>
> >> (1) http://www.oberhumer.com/opensource/lzo/
> >>
> >> Johannes Schindelin wrote:
> >> > Hi,
> >> >
> >> > On Tue, 4 Jul 2006, Christian MICHON wrote:
> >> >
> >> >> how about also adding lzma compression for qcow ?
> >> >
> >> > Why lzma? We already have a dependency on zlib, why not just
> >> take that?
> >> >
> >> > Ciao,
> >> > Dscho
> >> >
> >> >
> >> > _______________________________________________
> >> > Qemu-devel mailing list
> >> > Qemu-devel@nongnu.org
> >> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >>
> >>
> >> _______________________________________________
> >> Qemu-devel mailing list
> >> Qemu-devel@nongnu.org
> >> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >>
> >
> >
> > --
> > Christian
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Christian
next prev parent reply other threads:[~2006-07-11 11:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 2:45 [Qemu-devel] QCow v2 Nathaniel McCallum
2006-07-04 8:12 ` Johannes Schindelin
2006-07-04 8:49 ` Raphaël Rigo
2006-07-04 9:23 ` Fabrice Bellard
2006-07-04 10:44 ` Christian MICHON
2006-07-04 10:57 ` Fabrice Bellard
2006-07-04 11:28 ` Julian Seward
2006-07-04 11:01 ` Johannes Schindelin
2006-07-04 11:13 ` Elefterios Stamatogiannakis
2006-07-04 13:51 ` Christian MICHON
2006-07-04 15:04 ` Natalia Portillo
2006-07-11 11:30 ` Christian MICHON [this message]
2006-07-11 17:43 ` André Braga
2006-07-04 11:14 ` Christian MICHON
2006-07-04 11:26 ` Fabrice Bellard
2006-07-04 12:13 ` Christian MICHON
2006-07-04 12:22 ` Fabrice Bellard
2006-07-04 13:03 ` Christian MICHON
2006-07-04 13:16 ` Christian MICHON
2006-07-04 13:28 ` Johannes Schindelin
2006-07-04 13:01 ` Nathaniel McCallum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46d6db660607110430w74fa175avc0f01a52bb91f44a@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).