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
Currently, DKMS uses compression level 19 when ZSTD is selected as the compression method. However, this does not provide a significant benefit in terms of compressed size when compared to lower levels, especially when considering the time it takes to compress them:
As an example, here are the compression stats for nvidia-dkms on Arch Linux for compression levels -19 and -1.
IMO, a saving of only 4.2MiB is not really worth it when the compression takes under a second for -1 but nearly 2 minutes(!) for -19.1
This situation could be improved with either a lower compression level or by making the compression settings configurable (with some documentation of the compatibility concerns noted in #386)
Footnotes
Times are for my personal computer, with a threadripper 2950x @ 3.5GHz with PBO enabled, 64GB of 2933MHz ECC memory, and an nvme drive. ↩
The text was updated successfully, but these errors were encountered:
Currently, DKMS uses compression level 19 when ZSTD is selected as the compression method. However, this does not provide a significant benefit in terms of compressed size when compared to lower levels, especially when considering the time it takes to compress them:
As an example, here are the compression stats for
nvidia-dkms
on Arch Linux for compression levels-19
and-1
.with
-19
:with
-1
:IMO, a saving of only 4.2MiB is not really worth it when the compression takes under a second for
-1
but nearly 2 minutes(!) for-19
.1This situation could be improved with either a lower compression level or by making the compression settings configurable (with some documentation of the compatibility concerns noted in #386)
Footnotes
Times are for my personal computer, with a threadripper 2950x @ 3.5GHz with PBO enabled, 64GB of 2933MHz ECC memory, and an nvme drive. ↩
The text was updated successfully, but these errors were encountered: