-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide alternate, better compressed tarballs #1233
Comments
Nice evaluation! Instinctively I would have chosen Just to state the obvious...
$ unzip -d Noto Noto.zip
6,96s user 0,87s system 99% cpu 7,846 total
$ tar xvf Noto.tar.xz
5,94s user 2,21s system 127% cpu 6,387 total
$ tar xvf Noto.tar.zst
0,97s user 1,60s system 146% cpu 1,756 total |
About that.. I wanted to mention a couple things but the post was already quite long. In short, you are probably right that Moreover, the adoption for zstandard seems to be climbing. From wikipedia some notable adoption are:
And finally
Although I'm not sure how well supported zstandard compressed zip files are... On linux (and I assume BSDs too), installing But with all that being said, yes, it's true that either So although I'm quite impressed with zstandard's all round well performance, I'd still be content to have well compressed |
Maintenance-wise this is just one more line in the 'archive all the stuff' script. Dropping |
Taken from https://clearlinux.org/news-blogs/linux-os-data-compression-options-comparing-behavior, from 2017 |
Thanks for the link, it was interesting. However I'm a bit disappointed that the author didn't share the commands he used. XZ being able to compress a bit more aligns with my experience, but the "faster" part contradicts my experience completely. Perhaps the author didn't use multi-threading? (by default |
See #1233 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Unfortunately Homebrew seems to not support Also see In the Cask manual (which might or might not be up-to-date) it is not listed: |
Maybe @polyzen has an idea if the Arch packages would / could utilize |
Some additional data-point: gentoo requires Also FYI, |
Definitely can. Edit: blakkheim already switched over to them: archlinux/svntogit-community@3c60f2c |
I've switched over the nixpkgs package to use the new tarballs: NixOS/nixpkgs#231749 When building a derivation with all available fonts, it cut down the build time nearly in half: https://androiddev.social/@msfjarvis/110380158758015208 |
- Bump Nerd Fonts version to v3.0.1 - Use `tar.xz` archive format [`ryanoasis/nerd-fonts#1233`](ryanoasis/nerd-fonts#1233) - Move code to default linux font folder - Include template on MacOS font folder
See #1233 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
See #1233 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
See #1233 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
See #1233 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
The gentoo guru overlay also switched over to the |
👍 Somehow the bot failed to add you as contributor, I guess because you have two dashes in the name 🙄 |
See ryanoasis#1233 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference. |
Is your feature request related to a problem? Please describe.
Some of the nerd-font packages can be really large, for example the Iosevka font clocks in at
244MiB
on the latest release.This can be painful for people who have slow connection and/or limited bandwidth.
Describe the solution you'd like
It'd be great if the project can provide alternative tarballs with better compression methods. From my (somewhat limited) research,
zstandard
,lzip
andxz
seems to be good contender for that spot.To test things out, I've decided to go with VictorMono, which is currently 66MiB with the zip format (and 121MiB uncompressed).
To create the tarballs, I'm using the following commands. I'm also using
plzip
andpxz
, the parallel versions oflzip
andxz
for better compression speed. For zstandard, I'm using the default/referencezstd
package.As you can see, the size difference is massive compared to the default zip file!
Some test for decompression speed:
zstd
seems to be performing really well whilexz
andplzip
required noticeable amount of time to extract.Given these data, to me it seems like
zstd
would be the ideal choice. It gives compression ratio comparable with the alternatives while still being significantly faster to both decompress and compress.I understand that providing multiple variant of the same archive can add some maintenance burden, but given the fact that producing is a one time effort while there's going to be thousands of people consuming the result - I believe the effort will be well worth it.
Describe alternatives you've considered
(None)
Additional context
(None)
The text was updated successfully, but these errors were encountered: