From: Alexander Clouter <alex@digriz.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: better/faster kernel tarball compression
Date: Mon, 22 Mar 2010 12:00:51 +0000 [thread overview]
Message-ID: <jo2k77-9sp.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: 4BA741D7.9020008@wpkg.org
Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>
>> 403804160 linux-2.6.34-rc2.tar
>> 67479563 linux-2.6.34-rc2.tar.bz2
>> 58452531 linux-2.6.34-rc2.tar.lz
>
> Speaking of file sizes, xz[1] already provides better compression:
>
> xz -k -9 linux-2.6.34-rc2.tar
>
> 55320408 linux-2.6.34-rc2.tar.xz
>
> xz -e -k -9 linux-2.6.34-rc2.tar
>
> 54800808 linux-2.6.34-rc2.tar.xz
>
> One drawback of xz is that it's not multi-threaded, much like bzip2 or
> gzip; would be great if it could be changed.
>
For some time there has been a multi-threaded bzip2 called
pbzip2[1], for some time; hell even Debian has it :)
I have no idea why the original poster is trying to say how "all teh
awesome" his code is being faster, well 'duh' it is using all the cores
on $BOX rather than just a single one.
I would be interested in comparisons against pbzip2 and the amusingly
named pigz[2]...plus a bunch of memory use comparisons, my AR7 board
only has 16MB of RAM :)
Cheers
[1] http://compression.ca/pbzip2/ - supports stdio (de)compression
[2] http://www.zlib.net/pigz/ - no idea if this supports stdio
--
Alexander Clouter
.sigmonster says: Approved for veterans.
next prev parent reply other threads:[~2010-03-22 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 10:09 better/faster kernel tarball compression Tomasz Chmielewski
2010-03-22 12:00 ` Alexander Clouter [this message]
2010-03-23 23:21 ` Ersek, Laszlo
-- strict thread matches above, loose matches on Subject: below --
2010-03-21 21:27 Ersek, Laszlo
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=jo2k77-9sp.ln1@chipmunk.wormnet.eu \
--to=alex@digriz.org.uk \
--cc=linux-kernel@vger.kernel.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