You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
I'm currently adding automated testing of meta-swupd. One bottleneck is the slow compression of pack-os-core-from-0.tar with "bsdtar -J". It's single-CPU and fully occupies one CPU for a minute or more.
Given that the file is never actually getting published and (if at all) only used inside the same machine, would it make sense to make the compression level configurable, not just for this file but everywhere? Then unit tests that just do basic sanity testing and don't care about compression rates can be sped up by using a faster compression or even no compression at all.
The text was updated successfully, but these errors were encountered:
@bryteise Yes, there was some discussion recently about skipping compression steps entirely. I would also be in favor of making compression levels configurable, but the fact that swupd-server will try gzip/bzip2/xz and choose between the three, configurable levels for all supported compression types would be needed.
Depending on the test, creating the pack-os-core-from-0.tar can be skipped entirely because it is only needed for installing from scratch. I'll add that to meta-swupd.
But in general the feature request still stands.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm currently adding automated testing of meta-swupd. One bottleneck is the slow compression of pack-os-core-from-0.tar with "bsdtar -J". It's single-CPU and fully occupies one CPU for a minute or more.
Given that the file is never actually getting published and (if at all) only used inside the same machine, would it make sense to make the compression level configurable, not just for this file but everywhere? Then unit tests that just do basic sanity testing and don't care about compression rates can be sped up by using a faster compression or even no compression at all.
The text was updated successfully, but these errors were encountered: