Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: nnml compression: state of the art?
Date: Thu, 29 Mar 2001 17:26:52 -0500	[thread overview]
Message-ID: <01Mar29.173100est.115492@gateway.intersys.com> (raw)
In-Reply-To: <87bsqke4s8.fsf@wesley.springies.nom>

* Alan Shutko <ats@acm.org>  on Thu, 29 Mar 2001
| I disagree.  I tried it on a mail folder I have around:

Context: nnml files are generally ~4k, not 20MB.  A more relevant example:

-rw-------    1 ratinox  ratinox      4974 Mar 29 17:04 test
-rw-------    1 ratinox  ratinox      2640 Mar 29 17:04 test.1.gz
-rw-------    1 ratinox  ratinox      2557 Mar 29 17:04 test.9.gz

On a system like mine with 4k blocks, test requires two blocks (8k), while
test.1.gz and test.9.gz require one block (4k) each.  The net gain in free
space is one block (4k) regardess of -1 or -9.

On a system with 2k blocks, test requires three blocks (6k), while
test.1.gz and test.9.gz require two blocks (4k) each.  The net gain in free
space is one block (2k) regardless of -1 or -9.

On a system with 1k blocks, test requires five blocks (5k), while test.1.gz
and test.9.gz require three blocks (3k) each.  The net gain in free space
is two blocks (2k) regardless of -1 or -9.

On a system with 512 byte blocks, test requires 10 blocks (5k), while
test.1.gz requires 6 blocks (3k) and test.2.gz requires 5 blocks (2.5k).  A
net savings of 512 bytes.  This is reaching the point of diminishing
returns, because if test were 7 bytes longer then the gzip -9 file would be
slightly over 512 * 5 and require 6 blocks (3k), again for no net gain.

If you have a few very large files then gzip -9 is usually better if space
is the primary concern.  If you have lots and lots of small files then gzip
-1 is almost always better, except in a few odd cases.

By the way:

-rw-------    1 ratinox  ratinox      4974 Mar 29 17:04 test
-rw-------    1 ratinox  ratinox      2640 Mar 29 17:04 test.1.gz
-rw-------    1 ratinox  ratinox      2623 Mar 29 17:04 test.2.gz
-rw-------    1 ratinox  ratinox      2607 Mar 29 17:04 test.3.gz
-rw-------    1 ratinox  ratinox      2561 Mar 29 17:04 test.4.gz
-rw-------    1 ratinox  ratinox      2557 Mar 29 17:04 test.5.gz
-rw-------    1 ratinox  ratinox      2557 Mar 29 17:04 test.6.gz
-rw-------    1 ratinox  ratinox      2557 Mar 29 17:04 test.7.gz
-rw-------    1 ratinox  ratinox      2557 Mar 29 17:04 test.8.gz
-rw-------    1 ratinox  ratinox      2557 Mar 29 17:04 test.9.gz

Anything beyond -5 nets you no extra space savings for small files.
-- 
Rat <ratinox@peorth.gweep.net>    \ Do not use Happy Fun Ball on concrete.
Minion of Nathan - Nathan says Hi! \ 
PGP Key: at a key server near you!  \ 



  reply	other threads:[~2001-03-29 22:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-29  8:22 Bill White
2001-03-29 13:04 ` Karl Kleinpaste
2001-03-29 15:47 ` Stainless Steel Rat
2001-03-29 17:12   ` Randal L. Schwartz
2001-03-29 19:15     ` Stainless Steel Rat
2001-03-29 19:21       ` Paul Jarc
2001-03-29 22:01         ` Stainless Steel Rat
2001-03-30 13:01           ` Randal L. Schwartz
2001-03-29 19:46       ` Michael Livshin
2001-03-29 19:47       ` Alan Shutko
2001-03-29 22:26         ` Stainless Steel Rat [this message]
2001-03-30 10:44 ` Bill White

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=01Mar29.173100est.115492@gateway.intersys.com \
    --to=ratinox@peorth.gweep.net \
    /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).