From: "Daniel Schaefer" <daniel.schaefer@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: <derek.lin2@hpe.com>
Subject: Multithreaded compression with LZMA2
Date: Wed, 2 Dec 2020 10:59:45 +0800 [thread overview]
Message-ID: <a87105e7-be55-b66d-eee0-a9f495f705e8@hpe.com> (raw)
Hi everyone,
I'm looking into how to speed up the build process and noticed that our build
uses LZMA to encrypt the main firmware volume. Since it's quite big it takes a
while but only uses one CPU thread.
LZMA2 is a version of LZMA which can be multi-threaded and achieve much faster
compression times. I did a quick benchmark using the `xz` command-line tool,
which uses a modified version of the LZMA SDK that EDK2 uses. The results are:
Uncompressed size: 64M
| Algo | Comp Time | Decomp Time | Size | Threads |
| ----- | --------- | ----------- | ---- | ------- |
| LZMA | 19.67s | 0.9s | 9.1M | 1 |
| LZMA2 | 20.11s | 1.2s | 9.2M | 1 |
| LZMA2 | 8.31s | 1.0s | 9.4M | 4 |
Using those commands:
time xz --format=lzma testfile
time unlzma testfile.lzma
time xz --lzma2 testfile
time unxz testfile.xz
time xz -T4 --lzma2 testfile
time unxz testfile.xz
This is quite a significant improvement of build time, while decompression time
and size only slightly increase. If that's a concern, then LZMA2 could be used
for development only.
I haven't investigated the details of how to support this in the code but it
appears to be a simple change, since the LZMA SDK that we use already supports
LZMA2.
What do you think?
Thanks,
Daniel
next reply other threads:[~2020-12-02 3:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 2:59 Daniel Schaefer [this message]
2020-12-02 3:36 ` [edk2-devel] Multithreaded compression with LZMA2 Andrew Fish
2020-12-02 5:21 ` 回复: " gaoliming
2020-12-02 8:24 ` Daniel Schaefer
2020-12-03 10:24 ` Laszlo Ersek
2020-12-03 12:11 ` Daniel Schaefer
2020-12-03 15:57 ` Bret Barkelew
2020-12-04 8:19 ` Daniel Schaefer
2020-12-03 23:35 ` Laszlo Ersek
2020-12-04 2:28 ` 回复: " gaoliming
2020-12-04 9:02 ` Daniel Schaefer
2020-12-08 6:01 ` 回复: " gaoliming
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-list 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=a87105e7-be55-b66d-eee0-a9f495f705e8@hpe.com \
--to=devel@edk2.groups.io \
/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