mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Willy Tarreau <w@1wt.eu>,
	Drew Scott Daniels <ddaniels@UMAlumni.mb.ca>,
	linux-kernel@vger.kernel.org
Subject: Compressing pages [was: Re: Smaller compressed kernel source tarballs?]
Date: Wed, 4 Oct 2006 17:57:47 +0200	[thread overview]
Message-ID: <20061004155747.GA4096@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <4522AAC1.7050703@cfl.rr.com>

On Tue, 3 October 2006 14:24:01 -0400, Phillip Susi wrote:
> Jan Engelhardt wrote:
> >There are lots of obscure compression formats that achieve somewhat 
> >better compression at the cost of MUCH more time (neglecting they are 
> >not too open), such as MS CAB and ACE.
> 
> CAB is an archive container format, not a compression algorithm.  Last 
> time I worked on some code to handle it, they used the standard LZW 
> algorithm implemented by gzip ( but had the ability to support others in 
> the future ) and could only compress 32kb blocks.  The small block size 
> led to poor compression.

Actually, compression in 4KiB blocks is a _very_ interesting
benchmark.  Jffs2 works with that size for compression and other
compressed filesystems likely do the same, although possibly with
something larger like 64KiB.

And the results are completely different in that benchmark.  Gzip
actually beats bzip2 hands-down on compression ratio, for example.

I used to have a script, but cannot find it anymore.  Basically
something like:

while (read next 4KiB from input file) {
	compress chunk
	add compressed_size to total
}
print total

Jörn

-- 
Unless something dramatically changes, by 2015 we'll be largely
wondering what all the fuss surrounding Linux was really about.
-- Rob Enderle

      reply	other threads:[~2006-10-04 15:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02  3:35 Smaller compressed kernel source tarballs? Drew Scott Daniels
2006-10-02  3:32 ` Bernd Eckenfels
2006-10-02  3:35 ` Willy Tarreau
     [not found]   ` <Pi ne.LNX.4.63.0610012205280.28534@qynat.qvtvafvgr.pbz>
2006-10-02  5:11   ` David Lang
2006-10-02  5:49     ` Willy Tarreau
2006-10-02 15:16     ` Phillip Susi
2006-10-02 15:48       ` David Lang
2006-10-02 20:20         ` Phillip Susi
2006-10-02 20:12           ` David Lang
2006-10-02 20:35             ` Willy Tarreau
     [not found]             ` <2006 1002203527.GA585@1wt.eu>
2006-10-02 21:49               ` Sean
     [not found]                 ` <20061002174938.bb82027d.seanlkml@sympatico.ca>
2006-10-02 21:42                   ` David Lang
2006-10-03  2:48                   ` Willy Tarreau
2006-10-03 10:28   ` Jan Engelhardt
2006-10-03 18:24     ` Phillip Susi
2006-10-04 15:57       ` Jörn Engel [this message]

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=20061004155747.GA4096@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=ddaniels@UMAlumni.mb.ca \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psusi@cfl.rr.com \
    --cc=w@1wt.eu \
    /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

Powered by JetHome