public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Zstandard support for setup
Date: Fri, 17 Aug 2018 18:49:00 -0000	[thread overview]
Message-ID: <876008u8us.fsf@Rainer.invalid> (raw)
In-Reply-To: <874lg0d6l8.fsf@Rainer.invalid> (Achim Gratz's message of "Sat,	11 Aug 2018 21:52:03 +0200")


While it seems like I'm talking to myself, in case anybody is listening:

With the "normal" maximum compression level of 19 the package archive
for my installation (including sources and debuginfo) got about 10%
larger, taking about the same time as Xz for compression.  Using the
"ultra" compression level 22 gets that difference to about 3% at the
expense of twice the CPU time for the compression.  My repo is about
8GiB compressed and it took about 8 (resp. 16 hours) of single-core CPU
time to re-compress (uncompress from BZip2 or Xz and recompress
on-the-fly to ZStdandard).  The higher compression level needs just a
bit over 1.5GiB on average and around 3GiB peak.

I've had 16 cores to run that on and those stayed at 2.8GHz all the
time, so it didn't take too long.  Here at home I've tasked two slower
4-core machines with it, so they were running a few hours of wall-time.
I might try long-range matching to get even better compression at work
since I've got 128GB memory now to see if there's an improvement.  At
home I've run out of 8GiB memory more than once even with a single
compression for the largest debuginfo packages.  Incidentally, these
packages always take the longest time to compress, so if you want to do
a parallel mass conversion it's advisable to start these first (keeping
an eye on available memory) and have the faster compression of the
smaller package archives fill the remaining CPU/time.

I've installed and updated over a dozen of machines by now with this, so
I'm reasonably certain that the implementation in setup is OK.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  parent reply	other threads:[~2018-08-17 18:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11 19:52 Achim Gratz
2018-08-12 13:28 ` Achim Gratz
2018-08-17 18:49 ` Achim Gratz [this message]
2018-08-20 18:11   ` Marco Atzeri
2018-08-20 19:54     ` Achim Gratz
2018-08-22 19:12   ` Achim Gratz
2018-08-23 20:40 ` Achim Gratz
2018-08-29 16:42 ` Jon Turney
2018-09-02  8:31   ` Achim Gratz
2018-09-02 17:03     ` Achim Gratz
2018-10-07 19:46       ` Jon Turney
2018-10-09 18:04         ` Achim Gratz
2018-10-07 22:09     ` Jon Turney
2018-10-09 18:05       ` Achim Gratz
2018-10-10 18:37   ` Achim Gratz
2018-10-13 17:19     ` Jon Turney
2018-10-14 11:29       ` Achim Gratz

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=876008u8us.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).