public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup] Add new option '--compact-os'
Date: Thu, 13 May 2021 16:45:56 +0200	[thread overview]
Message-ID: <6c4644f5-d11a-5ef7-cc69-9d5f563af795@t-online.de> (raw)
In-Reply-To: <2c7ad892-b0ff-67e5-02f5-2c1afc596fce@t-online.de>

Christian Franke wrote:
> Corinna Vinschen via Cygwin-apps wrote:
>> ...
>> When running a shell script, certain executables (especially coreutils,
>> gawk, sed, grep, find) are not so very infrequently accessed. Is this
>> compression really feasible for these binaries?  Did you compare shell
>> script performance with non-compressed, XPRESS16K and LZX compressed
>> /bin dir?
>
> Good point. Now I did a test with a ./configure script run after 
> reboot: There was significant difference with /bin/*.exe (only) 
> uncompressed, NTFS-, XPRESS16K- or LZX-compressed. Time was always 
> around 23s.

Of course this should be: "... . There was *no* significant difference 
...", sorry.


  reply	other threads:[~2021-05-13 14:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 20:03 Christian Franke
2021-05-12 15:14 ` Jon Turney
2021-05-12 17:50   ` Christian Franke
2021-05-12 18:35     ` ASSI
2021-05-12 18:48       ` Achim Gratz
2021-05-13 15:09         ` Christian Franke
2021-05-13 14:55     ` Jon Turney
2021-05-14  7:27       ` Christian Franke
2021-05-14  7:55         ` Christian Franke
2021-07-18 13:44           ` Jon Turney
2021-05-12 18:04   ` Corinna Vinschen
2021-05-13 14:42     ` Christian Franke
2021-05-13 14:45       ` Christian Franke [this message]
2021-05-17 10:17       ` Corinna Vinschen

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=6c4644f5-d11a-5ef7-cc69-9d5f563af795@t-online.de \
    --to=christian.franke@t-online.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).