In my application I need do compress of logs that are text files.
Seems that bzip2 and gzip have the same compression ratio.
Is that correct?
feedback
|
This question came from our site for professional and enthusiast programmers.
|
Normally, bz2 has a better compression ratio, combined with better recoverability features. OTOH, gz is faster. xz is said to be even better than bz2, but I don't know the timing behaviour. | |||
|
feedback
|
|
Maybe you could have a look to those benchmarks, especially the part testing the log files compression. | |||
|
feedback
|
|
bz2 has tighter compression, the algorithm has more options to look for redundancy to compress away. gzip is in much more tools, and is more cross platform. More Windows tools can deal with .gz files. It's part of http, so even web browsers can understand it. On linux, there are tools that let you work on compressed files directly. zgrep and bzgrep can search in compressed files. If just on Linux, I'd use bzip2, for the slightly better compression ratios. | |||
|
feedback
|
|
xz compresses much better than bz2, but takes more time. So, if maximum compression is your goal and space on your hard drive is at a premium (which is my case with one drive at 98% full - while I reorganize my file systems), and you can fire off a script to do the work - take a break and come back in 5 minutes. unxz is very fast to uncompress in my experience - which is a good thing for me on a daily basis. bz2 is faster to compress than xz, but does not appear to achieve the compression results of xz. The only way to make these assessments is to run benchmarks against a mix of common files you normally would compress/decompress, and vary the parameters to see which comes out on top. | |||
|
feedback
|