2 ms·
It's not terribly useful for most applications to test compression speed. The only applications I can think of where this is relevant is data backup and archiv
by klodolph 10y ago
It's not terribly useful for most applications to test compression speed. The only applications I can think of where this is relevant is data backup and archiving.
There are two typical speed benchmarks you want to do. For the "compress once, decompress many times" situation, benchmark the time it takes to decompress and ignore compression time. For the "compress once, decompress once" situation, add the compression and decompression times.
The first situation is common for distributing packages and static assets, the second situation is common for distributing dynamic assets.
- eye2sky 10y agoFor the second situation, I prefer the compress/transmit/decompress metric (as a function of transmit pipe speed), as described here: http://fastcompression.blogspot.com/p/compression-benchmark.html http://fastcompression.blogspot.com/p/compression-benchmark....