From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup] Add new option '--compact-os'
Date: Mon, 17 May 2021 12:17:15 +0200 [thread overview]
Message-ID: <YKJCqyEhi6mabvxe@calimero.vinschen.de> (raw)
In-Reply-To: <2c7ad892-b0ff-67e5-02f5-2c1afc596fce@t-online.de>
On May 13 16:42, 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.
>
> Here a read speed test with fast and slow storage and a 10+ years old
> i7-2600K (4C/8T). The 256MiB test file was generated by concatenating
> various EXE files. All file accesses were the first after reboot. AV
> (defender) was turned off:
>
>
> Compression MiB T1 T2 T3,T4
> ======================================
> None 256 0.69s 10.1s <0.02s
> NTFS 159 1.03s 8.1s <0.02s
> XPRESS4K 138 -
> XPRESS8K 128 -
> XPRESS16K 123 0.64s 5.4s <0.02s
> LZX 97 0.79s 4.8s <0.02s
>
> T1,T2: Read whole file: time dd if=FILE bs=FILESIZE of=/dev/null
> T3,T4: Read last byte: time dd if=FILE bs=1 skip=FILESIZE-1 of=/dev/null
>
> T1,T3: SATA SSD, raw read speed with dd bs=1M: ~520MB/s
> T2,T4: USB3 flash drive via USB2, raw read speed: ~27MB/s
>
>
> As expected, compression helps to improve 'virtual' read speed on slow
> storage. Otherwise, it depends on storage speed, CPU speed, system load, ...
> As unexpected (for me), even LZX seems to be suitable for random reads which
> are done when EXE files are preloaded or paged-in.
>
> If the files were already cached, all read times were similar: ~0.135s for
> the whole file.
>
> For more flexibility, I will provide a new version of the patch with
> '--compact-os ALGORITHM' option.
Great, thanks!
Corinna
prev parent reply other threads:[~2021-05-17 10:17 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
2021-05-17 10:17 ` Corinna Vinschen [this message]
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=YKJCqyEhi6mabvxe@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).