(In reply to Johan Lorenzo [:jlorenzo] from comment #5) > (In reply to Artem S. Tashkinov from comment #3) > > You'll save a lot of space by converting to ZSTD. > > Thank you for bringing this up, Artem! I know cloud storage is usually cheap. That said, I don't know how much bandwidth we could save if we publish Linux archives that are 15% smaller. Tom, is this number easy to estimate for the CloudOps team? If not, what team should we reach out to? Yes, cloud storage is on the cheaper side but the bandwidth and CDN costs come into play as well to distribute it. It's not a quick estimate as we'd have to segment it out from the other items sharing the bandwidth and CDN. Honestly, if the level of effort is not that big, I don't see a downside into saving costs and speeding up decompression.
Bug 1710599 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Johan Lorenzo [:jlorenzo] from comment #5) > (In reply to Artem S. Tashkinov from comment #3) > > You'll save a lot of space by converting to ZSTD. > > Thank you for bringing this up, Artem! I know cloud storage is usually cheap. That said, I don't know how much bandwidth we could save if we publish Linux archives that are 15% smaller. Tom, is this number easy to estimate for the CloudOps team? If not, what team should we reach out to? Yes, cloud storage is on the cheaper side but the bandwidth and CDN costs come into play as well to distribute it. It's not a quick estimate as we'd have to segment it out from the other items sharing the bandwidth and CDN. Honestly, if the level of development effort is not that big, I don't see a downside into saving costs and speeding up decompression.