We’re excited to announce an improvement for our Linux users that enhances both performance and compatibility with various Linux distributions. Switching to .tar.xz Packaging for Linux Builds In our ongoing ...
I am curious too. You tested two different versions, one beta and the other current nightly (different content). It’s okay for a quick test, but you can actually have a much closer test. Both nightly and only one day difference:
I run this quick test multiple times and on average these are typical results (don’t forget to delete the unpacked folder between each runs):
$ time tar xjf firefox-135.0a1.en-US.linux-x86_64.tar.bz2
real0m5,784s
user0m5,700s
sys 0m0,371s
$ time tar xJf firefox-135.0a1.en-US.linux-x86_64.tar.xz
real0m1,699s
user0m1,621s
sys 0m0,315s
On my system that consistently gets results around 10s and 5s so the difference is sort of interesting. Mine’s a Ryzen 3600, maybe newer CPU features are of substantial benefit to xz.
I am curious too. You tested two different versions, one beta and the other current nightly (different content). It’s okay for a quick test, but you can actually have a much closer test. Both nightly and only one day difference:
I run this quick test multiple times and on average these are typical results (don’t forget to delete the unpacked folder between each runs):
$ time tar xjf firefox-135.0a1.en-US.linux-x86_64.tar.bz2 real 0m5,784s user 0m5,700s sys 0m0,371s $ time tar xJf firefox-135.0a1.en-US.linux-x86_64.tar.xz real 0m1,699s user 0m1,621s sys 0m0,315sOn my system that consistently gets results around 10s and 5s so the difference is sort of interesting. Mine’s a Ryzen 3600, maybe newer CPU features are of substantial benefit to xz.