The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Jeff Johnson" <trnsz@pobox.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: "Webster's Second on the Head of a Pin"?
Date: Tue, 11 Mar 2025 10:47:01 -0400	[thread overview]
Message-ID: <2152f633-b9c0-43a7-953e-3a4260b98b77@app.fastmail.com> (raw)
In-Reply-To: <CAKH6PiV2qQGvDd+PNDBYYeEfZ8pBTb8KVx2=YNNsVe4ma7-+cg@mail.gmail.com>

As far as getting maximum compression from lzip, `lzip -9 -s 512Mi`
is usually the preferred invocation.  I think the default dictionary
size at -9 is 64MiB, but that's not that relevant I guess, unless
we are comparing different methods and trying to see about what
ratios different algorithms get at similar memory usage.  

--
Jeffrey H. Johnson
trnsz@pobox.com

On Mon, Mar 10, 2025, at 8:23 PM, Douglas McIlroy wrote:
> Gnu lzip -9  got a 3.92 compression factor , while Morris-Thompson got 4.52.

--
Jeffrey H. Johnson
trnsz@pobox.com

On Mon, Mar 10, 2025, at 8:23 PM, Douglas McIlroy wrote:
> Gnu lzip -9  got a 3.92 compression factor , while Morris-Thompson got 4.52.

  reply	other threads:[~2025-03-11 14:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29  2:53 [TUHS] " Royce Williams
2024-12-29 13:44 ` [TUHS] " Douglas McIlroy
2024-12-30 21:13   ` sjenkin
2024-12-31 16:37   ` Chet Ramey via TUHS
2025-01-01 15:02     ` Douglas McIlroy
2025-01-01 18:11       ` Rik Farrow
2025-01-02  3:05         ` Douglas McIlroy
2025-01-02 14:28           ` Chet Ramey via TUHS
2025-01-02 14:22         ` Chet Ramey via TUHS
2025-01-02 18:13           ` Rik Farrow
2025-01-02 19:47             ` Chet Ramey via TUHS
2024-12-29 16:05 ` Douglas McIlroy
2025-03-10 22:55   ` James Johnston
2025-03-11  0:23     ` Douglas McIlroy
2025-03-11 14:47       ` Jeff Johnson [this message]
2025-03-12 12:41         ` Douglas McIlroy
2024-12-30  0:37 ` Warren Toomey via TUHS
2024-12-30  2:07   ` Royce Williams

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=2152f633-b9c0-43a7-953e-3a4260b98b77@app.fastmail.com \
    --to=trnsz@pobox.com \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).