mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	linux-kernel@vger.kernel.org, apiszcz@solarrain.com
Subject: Re: In response to kernel compression e-mail a few months ago.
Date: Sun, 14 Oct 2007 16:58:58 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710141650500.12466@p34.internal.lan> (raw)
In-Reply-To: <20071014205008.GZ8181@ftp.linux.org.uk>



On Sun, 14 Oct 2007, Al Viro wrote:

> On Sun, Oct 14, 2007 at 09:46:15PM +0200, Jan Engelhardt wrote:
>> (Obviously we shall pick .7z)
>
> The hell it is.  Take a look at memory footprint of those suckers...
>

For compression with -mx=9 it does use 500-900 MiB of RAM, that is true.
For decompression, 50-70 MiB.

Each have their pros/cons but nothing can compress the kernel any further 
than 7z, supports stdin/stdout and also has a native windows port.  I used 
to strictly use bzip2 for backups and such but if I can pick off an 
additional 20-30% more than bzip2 for my backups which I will not use often,
7zip seems to be the winner for space savings and possibly for 
bandwidth/cost savings..

compress:
   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
10544 war       20   0  700m 681m 1632 S  141 20.7   1:41.46 7z

decompress:
   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
11927 war       20   0 71256  66m 1536 R   88  2.0   0:04.07 7z

Justin.

  reply	other threads:[~2007-10-14 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 19:34 Justin Piszcz
2007-10-14 19:46 ` Jan Engelhardt
2007-10-14 19:53   ` Justin Piszcz
2007-10-14 20:04     ` Jan Engelhardt
2007-10-14 20:16       ` Justin Piszcz
2007-10-14 20:50   ` Al Viro
2007-10-14 20:58     ` Justin Piszcz [this message]
2007-10-14 21:48       ` Jan Engelhardt
2007-10-14 22:28         ` Justin Piszcz
2007-10-16 13:19       ` Denys Vlasenko
2007-10-16 13:31         ` Andreas Schwab
2007-10-16 20:54           ` Denys Vlasenko
2007-10-16 14:22         ` Jan Engelhardt

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=Pine.LNX.4.64.0710141650500.12466@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=apiszcz@solarrain.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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

all inboxes | Powered by JetHome®