lrzip-next vs lrzip vs xz, zpaq, zstd #83
pete4abw
started this conversation in
Show and tell
Replies: 2 comments 1 reply
-
Hello Peter,
Thank you |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Introduction
There are so many ways to compare, dissect, and discuss compression values. But sometimes numbers, not words tell the tale. One big difference between
lrzip-next
and the others is the pre-compressionrzip
hash phase. The original versions oflrzip
would have the rzip compression level set to the lrzip compression level. So level 4 compression would have level 4 rzip compression, and so on.lrzip-next
, however, can set rzip compression independently using the-R#
option. This can mean greater compression altogether as the tables below show.File types can impact performance
For this analysis, I took the entire linux kernel 5.x source code set from 5.4.x all the way to 5.19. The 5 tarballs totaled over 5GB in size. Binary type files or mixed files would perform differently. Since
lrzip-next
has filter options to preprocess the data to be compressed, additional benefits can be derived (e.g. using--x86
). Test system had an Intel(R) Core(TM) i7-1065G7 CPU with 16G of ram, compressing on an SSD.lrzip-next
version tested is 0.9.1.lrzip
version tested is 0.651.Results
Results are contained in two tables. One with actual values and one with various computed indexes that compare performance in different ways. The Size and Time indexes are derived by comparing the compressed size with the worst compressed size, and the fastest compression time to the slowest compression time.Best compression and times are bold. Worst compression and times are bold/italic
Performance table
Ratio
MB/s
Index table
This table introduces index comparisons. The lower the index value, the better. The worst Compression and Time indexes are scored 100. The overall index is an average of the size and time indexes. The weighted index halves the time and size indexes respectively to give weight to the other metric.
Conclusion
Two things are obvious.
lrzip-next
andlrzip
outperform the native programs.-R#
option greatly improveslrzip-next
performance as it consistently outperforms all others.Beta Was this translation helpful? Give feedback.
All reactions