From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] link to .xz files to save some bandwidth
Date: Tue, 7 Feb 2017 10:51:39 -0600 [thread overview]
Message-ID: <b7fc7007-1663-b41d-422a-9600e44d7b38@redhat.com> (raw)
In-Reply-To: <20170207155956.21573-1-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On 02/07/2017 09:59 AM, Paolo Bonzini wrote:
> I have converted all .gz and .bz2 files to .xz on download.qemu.org
> and this patch would change the links in the website. This would save
> about 5 GB of bandwidth every day (about 20% savings).
>
> xz should be available for all platforms. Besides providing better
> compression ratios, decompression of .xz files is about twice as fast
> compared to bzip2. Compression instead is about 5.5 times slower.
I agree that bzip2 is pointless these days; .gz is a bit more important
when targetting older platforms but I think that does not describe
qemu's target audience. Do we want to even enter the xz vs. lzma
controversy, or are we okay with being xz-only?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-02-07 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 15:59 [Qemu-devel] [PATCH] link to .xz files to save some bandwidth Paolo Bonzini
2017-02-07 16:51 ` Eric Blake [this message]
2017-02-08 8:49 ` Markus Armbruster
2017-02-08 9:29 ` Laszlo Ersek
2017-02-08 13:44 ` Eric Blake
2017-02-08 0:43 ` Michael Roth
2017-02-08 8:07 ` Paolo Bonzini
2017-02-08 10:17 ` Laszlo Ersek
2017-02-08 10:29 ` Daniel P. Berrange
2017-02-08 16:05 ` Paolo Bonzini
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=b7fc7007-1663-b41d-422a-9600e44d7b38@redhat.com \
--to=eblake@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.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).