Hi, ALL.
I have submitted a patchhttp://gerrit.ovirt.org/4174 it is about "make compression type configurable, support gzip and xz"
As I mentioned in message that vdsm require "xz" for logrotate. So I think there is no need to support two kinds of compression format: xz and gzip.
I have get some comments on this patch.
It seems xz is better. XZ utils supports multi threading, and the compression ratio is better than gzip. And it is supports many platforms (seehttp://tukaani.org/xz/ , look for Supported platforms).
Since xz gets higher compression efficiency and the logrotate has already required "xz" So how about to abandon gzip, only use xz?
Hi, ALL.
I have submitted a patch http://gerrit.ovirt.org/4174 it is about "make compression type configurable, support gzip and xz"
As I mentioned in message that vdsm requires "xz" for logrotate. So I think there is no need to support two kinds of compression format: xz and gzip.
I have get some comments on this patch.
It seems xz is better. XZ utils supports multi threading, and the compression ratio is better than gzip. And it is supports many platforms (see http://tukaani.org/xz/ , look for Supported platforms).
Since xz gets higher compression efficiency and the logrotate has already required "xz" So how about to abandon gzip, only use xz?
----- Original Message -----
From: "Sheldon" shaohef@linux.vnet.ibm.com To: vdsm-devel@lists.fedorahosted.org Sent: Monday, November 5, 2012 9:34:04 AM Subject: [vdsm] [VDSM][RFC]Switch of VDSM tarball compression format: tar.xz only
Hi, ALL.
I have submitted a patch http://gerrit.ovirt.org/4174 it is about "make compression type configurable, support gzip and xz"
As I mentioned in message that vdsm requires "xz" for logrotate. So I think there is no need to support two kinds of compression format: xz and gzip.
I have get some comments on this patch.
It seems xz is better. XZ utils supports multi threading, and the compression ratio is better than gzip. And it is supports many platforms (see http://tukaani.org/xz/ , look for Supported platforms).
Since xz gets higher compression efficiency and the logrotate has already required "xz" So how about to abandon gzip, only use xz?
The question can be why not use gzip and only gzip.
The SOURCES of vdsm is not something that gain much from either compression method. On BUILD machine it is better to have minimum requirement.
You are confusing between the RUNTIME machine and the BUILD machine if you consider the source tarball compression and the logrotate usage.
Anyway, to distribute source in multiple formats you only need to use the following options in Makefile.am: --- AUTOMAKE_OPTIONS = dist-xz ---
And not use complex patch as you proposed.
This will produce both gz and xz tarballs, for developers to chose what to use.
It save 300K!!! does it worth it? I think no.
Regards, Alon.
On Mon, Nov 05, 2012 at 03:31:23PM +0800, Sheldon wrote:
Hi, ALL.
I have submitted a patchhttp://gerrit.ovirt.org/4174 it is about "make compression type configurable, support gzip and xz"
As I mentioned in message that vdsm require "xz" for logrotate. So I think there is no need to support two kinds of compression format: xz and gzip.
I have get some comments on this patch.
It seems xz is better. XZ utils supports multi threading, and the compression ratio is better than gzip. And it is supports many platforms (seehttp://tukaani.org/xz/ , look for Supported platforms).
Since xz gets higher compression efficiency and the logrotate has already required "xz" So how about to abandon gzip, only use xz?
I don't really understand your motivation. Practically every open source project on the face of this planet, ships its source as a gzip'ed tarball. Which projects use xz for that?
Dan.
Hi,
On 11/05/2012 10:22 AM, Dan Kenigsberg wrote:
I don't really understand your motivation.
I also think that supporting gzip is important.
Practically every open source project on the face of this planet, ships its source as a gzip'ed tarball. Which projects use xz for that?
xz is the new hot compression (like 7zip was a few years ago, and bz2 was before it). GNOME has switched to xz tarballs only: https://mail.gnome.org/archives/devel-announce-list/2011-September/msg00003.... and other projects are moving in the same direction.
Just a data point.
Cheers, Dave.
----- Original Message -----
From: "Dave Neary" dneary@redhat.com To: "Dan Kenigsberg" danken@redhat.com Cc: vdsm-devel@lists.fedorahosted.org Sent: Friday, November 9, 2012 12:42:51 PM Subject: Re: [vdsm] [VDSM][RFC]Switch of VDSM tarball compression format: tar.xz only
Hi,
On 11/05/2012 10:22 AM, Dan Kenigsberg wrote:
I don't really understand your motivation.
I also think that supporting gzip is important.
Practically every open source project on the face of this planet, ships its source as a gzip'ed tarball. Which projects use xz for that?
xz is the new hot compression (like 7zip was a few years ago, and bz2 was before it). GNOME has switched to xz tarballs only: https://mail.gnome.org/archives/devel-announce-list/2011-September/msg00003.... and other projects are moving in the same direction.
Gnome is not example for anything... but apart of that this project contains a lot of binary artifacts and huge distribution, which is totally unrelated to vdsm.
In most cases hot != best
Alon
vdsm-devel@lists.fedorahosted.org