Comment 6 for bug 1932329
Revision history for this message
| Dimitri John Ledkov (xnox) wrote Re: Benchmark if we can compress kernel modules | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
79ea94a
(Get the code!)
Whilst download size is larger, it is at no additional cost to our end users, especially in the cloud. Majority of our clouds offer free transfers inside the availability zone for which mirrors are provided. Obviously it will increase the disk/cache storage size requirements of our mirrors.
Our end users have about 3 sets of kernels installed on disk, for which they do pay more per GB between 2 to 12 cents (depending on technology IOPS / hdd / sda / nvme). All things being equal our users would choose larger download sizes to gain smaller install size.
I assume that we have vastly larger install base, compared to number of our mirrors.
I also hope that our install base is not larger than the total bandwidth available of our mirrors, such that this switch would cause collapse of our mirror network.
I also notice that kernel uses default options for zstd module compression, instead of using -19 like it recommends for the initrds.
I also notice that kmod in focal doesn't support zstd.
Imho we should fix above before turning this on.