| May 23, 2010 10:00 AM PDT | |
Basic properties LZO:
- Very fast compression. No need of encoded dictionary
- Decompression is very fast; in non-trivial cases able to exceed the speed of a straight memory-to-memory copy due to the reduced memory-reads.
- Very fast compression. No need of encoded dictionary
- Decompression is very fast; in non-trivial cases able to exceed the speed of a straight memory-to-memory copy due to the reduced memory-reads.
- Decompression requires no additional memory other than the source and destination buffers.
- Allows the user to adjust the balance between compression quality and compression speed, without affecting the speed of decompression
Restriction of LZO:
Compression ratio is pretty low (~50%) compare with others compressions algorithms (like ZLIB as an example)
Restriction of LZO:
Compression ratio is pretty low (~50%) compare with others compressions algorithms (like ZLIB as an example)
As an example of efficiency of this algorithm implementation, see below ( Fig.1 )the Performance results obtained on Core i7 CPU ( Nehalem), Linux 64, Intel® IPP v.7.0.
Lower is better.
Figure 1
where are:
Orig LZO – original LZO implementation
IPP LZO ST – single threaded IPP-based LZO implementation
IPP LZO MT-X – threaded IPP-based LZO implementation, where X is 2,4 and 8 threads.
IPP LZO MT-X – threaded IPP-based LZO implementation, where X is 2,4 and 8 threads.
These are the so called the average data for all Calgary Corpus dataset.
Do you need more help?
This article applies to: Intel® Integrated Performance Primitives Knowledge Base
For more complete information about compiler optimizations, see our Optimization Notice.
Comments (0) 
Trackbacks (0)
Leave a comment 
To obtain technical support, please go to Software Support.
Author
Gennady Fedorov (Intel)
| ||
Sergey Khlystov@Intel
|
Tags for this Page


