In the last two columns (Part 1, Part 2), we contrasted a number of compression tools that you might use to free up disk space on your systems. In comparing compression utilities, the most important issues to consider are speed, the compression ratio (how much space you can expect to save), portability and reliability. Which of these factors ranks highest in your list depends on your application, but the compression tool that you use routinely should work well on most of the files that you need to compress, giving you reasonably good file size reduction and acceptable performance.

What we didn't consider in the earlier columns were decompression time (we looked only at compression time) and the possibility that some of the compression utilities may not work at all given extremely large files. We also didn't get into the issue of patent restrictions -- whether there are hidden strings attached to your use of particular compression tools.

Decompression Timing

With respect to timing, decompression time can be considerably more important than compression time. Why? Because the files that you compress may be delivered to any number of individual users or customers. In other words, every file that is compressed may be uncompressed tens or hundreds of times and is likely to be uncompressed at considerably more time-critical moments.

In glossing over the issue of decompression time, we might have assumed that compression and compression times would be roughly equivalent for any particular compression tool. This assumption, however, proves not to be the case, particularly with very large files. For some compression tools, the compression operation takes MUCH longer than the corresponding decompression. For others, the compression may be slightly faster. For every tool, however, the contents of a file, not just its size, determines how quickly it will be compressed and decompressed by the particular tool. The script presented last week has, therefore, been modified and presented again below -- this time measuring decompression time along with compression time with some surprising results.

Working with Very Large Files

If the files that you need to compress are particularly large, you may need to verify that the tool you want to use can compress and decompress them. Some compression utilities may break down when asked to process extremely large files. For example, the pack command may issue the following error message when asked to compress a 2 Gbyte file -- a reference to limitations of the particular compression algorithm (Huffman encoding) that it uses:

Huffman tree has too many levels - file unchanged

Working with Very Small Files

If the files that you need to work with are particularly small, you may see little or no space saving from compressing them. In fact, some files will even grow in size if you force a compression (some tools will simply not operate on files that are extremely small) -- as shown here.

First, we create an empty file:

> touch zerobytes

Then, we attempt to "compress" it, but the compress command

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine