feat: remove rootfs.tar compression/decompression step#253
feat: remove rootfs.tar compression/decompression step#253gagath wants to merge 1 commit intoqualcomm-linux:mainfrom
Conversation
gzip compression only uses a single core, and we are decompressing the rootfs right after when building an image taking the rootfs as its input. On my build machine, here are the timings saved: - compression: 128 s - decompression: 48 s The Makefile rules are updated to reflect the change. The CI workflow is updated to compress the rootfs before staging it as an artifact for upload, saving some bandwidth and storage space only where it seems necessary. This commit is the first work regarding trying to reduce the number of compression/decompression cycles described in qualcomm-linux#246. Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
9a07a3c to
3470ded
Compare
Test jobs for commit 9a07a3c |
Test Results 2 files ±0 6 suites ±0 2m 54s ⏱️ ±0s For more details on these failures, see this check. Results for commit 3470ded. ± Comparison against base commit aa30037. |
Test jobs for commit 3470ded |
|
FWIW, |
We would still be compressing to decompress it right away. I even considered lz4 to go super fast, but what’s the point? The only use of compressing it seems to be to reduce artifacts size in CI. |
|
Removing draft status, the CI failure is a false positive now documented in #254. |
|
Looks good. Thanks! |
gzip compression only uses a single core, and we are decompressing the rootfs right after when building an image taking the rootfs as its input.
On my build machine, here are the timings saved:
The Makefile rules are updated to reflect the change.
The CI workflow is updated to compress the rootfs before staging it as an artifact for upload, saving some bandwidth and storage space only where it seems necessary.
This commit is the first work regarding trying to reduce the number of compression/decompression cycles described in #246.