Jump to content

LZO: Difference between revisions

From EDM2
Created page with "A run time compression C library that is also available in a Java implementation that offers fairly moderate compression in return for high compression and decompressi..."
 
No edit summary
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
A run time compression [[C]] library that is also available in a [[Java]] implementation that offers fairly moderate compression in return for high compression and decompression speeds. Intended to be used for internal data compression in databases and similar applications rather than file compression, but in those sort of cases a low load decompression can in addition to saving space actually speed up reading and writing to and from slow peripherals such as hard drives.
{{Software
|Picture=NA.png
|Name=LZO
|Version=2.10 (Mar 2017)
|Vendor=
|Author=Markus F.X.J. Oberhumer
|Licence=[[GPL v2]]
|WWW=http://www.oberhumer.com/opensource/lzo/
}}
'''LZO''' is a run-time compression [[C]] library that is also available in a [[Java]] implementation that offers fairly moderate compression in return for high compression and decompression speeds. Intended to be used for internal data compression in databases and similar applications rather than file compression, but in those sort of cases a low load decompression can in addition to saving space actually speed up reading and writing to and from slow peripherals such as hard drives.


The LZO C library appears to compile fairly cleanly on OS/2 with the usual caveats about compiler and system differences and so on, and in fact was commonly used in a number of open source projects on eComStation. However due to the fact that the code is licensed under the GPL and can therefore only be used in other GPL projects and the emergence of the [[Snappy]] and [[LZ4]] packages that offer similar amount of compression and compression speeds, coupled with much faster decompression speeds from the latter packages, its use has all but disappeared, even in GPL'd projects that used to use it internally. And for those same reason you are not recommended to use LZO unless you need to support legacy software that uses it.  
The LZO C library appears to compile fairly cleanly on OS/2 with the usual caveats about compiler and system differences and so on, and in fact was commonly used in a number of open source projects. However because the code is licensed under the GPL and can therefore only be used in other GPL projects and the emergence of the [[Snappy]] and [[LZ4]] packages that offer similar amount of compression and compression speeds, coupled with much faster decompression speeds from the latter packages, its use has all but disappeared, even in GPL'd projects that used to use it internally. And for those same reason you are not recommended to use LZO unless you need to support legacy software that uses it.


====miniLZO====
==Version==
miniLZO is a lightweight version of the LZO library, it consists of only one C source file and three header files and should add only about 6k to your executable. Compiles fine on OS/2 but the same caveats apply as with the full blown version.
* 2.0.9 (2015-02-04)
* 2.10 (2017-03-17)


==Version==
==See also==
* LZO 2.0.9 (2015-02-04)
* [[miniLZO]] - lightweight LZO
* [[Snappy]] - Similar C++ library
* [[LZ4]] - Similar C library


==Links==
==Links==
* [http://www.oberhumer.com/opensource/lzo/ LZO homepage]
* [http://www.oberhumer.com/opensource/lzo/ LZO homepage]
* [https://github.com/shevek/lzo-java Reimplementation in Java]]
* [https://github.com/shevek/lzo-java Reimplementation in Java]]
====See also====
* [[Snappy]] - Similar C++ library
* [[LZ4]] - Similar C library.


==Publications==
* [http://blog.erdemagaoglu.com/post/4605524309/lzo-vs-snappy-vs-lzf-vs-zlib-a-comparison-of A comparison of Java implementations of LZO, Snappy, LZ4 and zLib] - Differences apparently not as great as with the original C/C++ implementations
* [http://blog.erdemagaoglu.com/post/4605524309/lzo-vs-snappy-vs-lzf-vs-zlib-a-comparison-of A comparison of Java implementations of LZO, Snappy, LZ4 and zLib] - Differences apparently not as great as with the original C/C++ implementations


==License and status==
[[Category:Compression]][[Category:Software written in C]][[Category:Open Source Software]][[Category:C Libraries]]
* Open source software made available under the [[GPL v2]] - Active development.
 
==Authors==
* Markus F.X.J. Oberhumer (Original author)
* Shevek (Java port)
 
[[Category:Tools]][[Category:Compression]][[Category:Software written in C]][[Category:Open Source Software]][[Category:MS Windows Tools]][[Category:BeOS Tools]][[Category:Generic Unix Tools]][[Category:Amiga Tools]][[Category:Atari ST Tools]][[Category:C]][[Category:DOS Tools]][[Category:Java Tools]]

Latest revision as of 03:11, 26 May 2022

LZO
Name LZO
Version 2.10 (Mar 2017)
Vendor
Author Markus F.X.J. Oberhumer
Licence GPL v2
WWW http://www.oberhumer.com/opensource/lzo/

LZO is a run-time compression C library that is also available in a Java implementation that offers fairly moderate compression in return for high compression and decompression speeds. Intended to be used for internal data compression in databases and similar applications rather than file compression, but in those sort of cases a low load decompression can in addition to saving space actually speed up reading and writing to and from slow peripherals such as hard drives.

The LZO C library appears to compile fairly cleanly on OS/2 with the usual caveats about compiler and system differences and so on, and in fact was commonly used in a number of open source projects. However because the code is licensed under the GPL and can therefore only be used in other GPL projects and the emergence of the Snappy and LZ4 packages that offer similar amount of compression and compression speeds, coupled with much faster decompression speeds from the latter packages, its use has all but disappeared, even in GPL'd projects that used to use it internally. And for those same reason you are not recommended to use LZO unless you need to support legacy software that uses it.

Version

  • 2.0.9 (2015-02-04)
  • 2.10 (2017-03-17)

See also

Links