From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: scallywag / cygport not pulling lzip
Date: Fri, 08 Jan 2021 18:13:22 +0100 [thread overview]
Message-ID: <87a6tj9wst.fsf@Rainer.invalid> (raw)
In-Reply-To: <ffc9a4ea-3d6d-b7cf-4f2f-00a0f3df834c@SystematicSw.ab.ca> (Brian Inglis's message of "Fri, 8 Jan 2021 09:52:27 -0700")
Brian Inglis writes:
>> Yeah, perhaps lzip should be a dependency of cygport.
Since it promises to enable it's use, yes. I wouldn't mind to add a
dependency to tar also.
> ...and zstd as Achim is working on that.
That dependency has already been added to tar, so there is no need to do
anything special.
[as you could hav seen by looking at any of the recent CI logs]
> I do not think we should encourage use of lower compression ratio
> packages in cygport and calm, and their libraries in setup.
> It appears zstd gives up compression to gain faster decompression with
> less memory which may be advantageous for loading a kernel, but less
> optimal for MBs of base packages.
That difference is in the order of 3% over the full distribution at the
highest compression setting and roughly 5% is you use a compression
setting that is about as slow as xz. The installation time on the other
hand is dramatically shorter with zstd.
> Perhaps consideration should also be given to setting appropriate
> compression defaults in cygport for all supported package compressors
> e.g. GZIP=-9, XZ_OPT=-7 which does not increase the memory required
> from the default -6 but improves compression, ZSTD_CLEVEL=19 and
> ZSTD_NBTHREADS=`nproc` perhaps?
It is relatively useless to have zstd run with multiple threads in
compression mode since a lot of what takes time there is inherently
single threaded. It already does use an I/O thread to keep the data
pipes fed unless you specifically forbid that.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2021-01-08 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 7:38 Marco Atzeri
2021-01-08 13:23 ` ASSI
2021-01-08 13:58 ` Marco Atzeri
2021-01-08 14:21 ` Jon Turney
2021-01-08 16:52 ` Brian Inglis
2021-01-08 17:13 ` Achim Gratz [this message]
2021-01-08 18:09 ` Brian Inglis
2021-01-08 19:11 ` Achim Gratz
2021-01-11 22:05 ` Brian Inglis
2021-01-12 16:28 ` Brian Inglis
2021-01-12 19:46 ` ASSI
2021-01-09 19:08 ` Achim Gratz
2022-08-14 19:07 Hannes Mueller
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=87a6tj9wst.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).