| LZ4 | |
|---|---|
| Original author | Yann Collet |
| Developer | Yann Collet |
| Initial release | 24 April 2011 |
| Stable release | 1.10.0[1] 
/ 22 July 2024 |
| Written in | C |
| Operating system | Cross-platform |
| Platform | Portable |
| Type | Data compression |
| License | Simplified BSD License |
| Website | lz4 |
| Repository | |
| LZ4 Frame Format | |
|---|---|
| Magic number | 04 22 4D 18 (new)02 21 4C 18 (legacy)[2] |
| Type of format | Data compression |
| Website | https://github.com/lz4/lz4/blob/master/doc/lz4_Frame_format.md |
LZ4 is a lossless data compression algorithm optimized for fast compression and decompression. It belongs to the LZ77 family of byte-oriented compression schemes.
Features
editThe LZ4 algorithm provides a good trade-off between speed and compression ratio. Typically, it has a smaller (i.e., worse) compression ratio than the similar LZO algorithm, which in turn is worse than algorithms like DEFLATE. However, LZ4 compression speed is similar to LZO and several times faster than DEFLATE, while decompression speed is significantly faster than LZO.[3]
Design
editLZ4 only uses a dictionary-matching stage (LZ77) and, unlike other common compression algorithms, does not combine it with an entropy coding stage (e.g. Huffman coding in DEFLATE).[4][5]
The LZ4 algorithm represents the data as a series of sequences. Each sequence begins with a one-byte token that is broken into two 4-bit fields. The first field represents the number of literal bytes that are to be copied to the output. The second field represents the number of bytes to copy from the already decoded output buffer (with 0 representing the minimum match length of 4 bytes). A value of 15 in either of the bitfields indicates that the length is larger and there is an extra byte of data that is to be added to the length. A value of 255 in these extra bytes indicates that yet another byte is to be added. Hence, arbitrary lengths are represented by a series of extra bytes containing the value 255. The string of literals comes after the token and any extra bytes needed to indicate string length. This is followed by an offset that indicates how far back in the output buffer to begin copying. The extra bytes (if any) of the match-length come at the end of the sequence.[6][7]
Compression can be carried out in a stream or in blocks. Higher compression ratios can be achieved by investing more effort in finding the best matches. This results in both a smaller output and faster decompression.
LZ4 has two frame formats. The legacy format was very restrictive and relied on an external end-of-file signal, which proved to be a problem in Linux initramfs requiring a workaround to handle zero-padding.[8] The new format is a lot more flexible and has its own end-of-frame marker. It resembles the Zstd frame format in design.[9]
Implementation
editThe reference implementation in C by Yann Collet is licensed under a BSD license. There are ports and bindings in various languages including Java, C#, Rust, and Python.[10] The Apache Hadoop system uses this algorithm for fast compression. LZ4 was also implemented natively in the Linux kernel 3.11.[11] The FreeBSD, Illumos, ZFS on Linux, and ZFS-OSX implementations of the ZFS filesystem support the LZ4 algorithm for on-the-fly compression.[12][13][14][15] Linux supports LZ4 for SquashFS since 3.19-rc1.[16] LZ4 is also supported by the newer zstd command line utility by Yann Collet, as well as a 7-Zip fork called 7-Zip-zstd.[17]
References
edit- ^ "LZ4 v1.10.0 - Multicores edition". 22 July 2024. Retrieved 23 July 2024.
- ^ Collet, Yann. "LZ4 Frame Format Description". GitHub. Retrieved 7 October 2020.
- ^ Michael Larabel (28 January 2013). "Support For Compressing The Linux Kernel With LZ4". Phoronix. Retrieved 28 August 2015.
- ^ Collet, Yann (30 March 2019). "LZ4 Block Format Description". GitHub. Retrieved 9 July 2020.
There is no entropy encoder back-end nor framing layer.
- ^ DEFLATE Compressed Data Format Specification version 1.3. IETF. doi:10.17487/RFC1951. RFC 1951. Retrieved 9 July 2020.
- ^ Yann Collet (26 May 2011). "RealTime Data Compression". Retrieved 28 August 2015.
- ^ ticki (25 October 2016). "How LZ4 works". Retrieved 29 June 2017.
- ^ "lz4/doc/lz4_Frame_format.md at dev · lz4/lz4". GitHub.
- ^ "LZ4 Frame Format Description".
- ^ Extremely Fast Compression algorithm http://www.lz4.org on GitHub
- ^ Jonathan Corbet (19 July 2013). "Kernel development". LWN.net. Retrieved 28 August 2015.
- ^ "FreeBSD 9.2-RELEASE Release Notes". FreeBSD. 13 November 2013. Retrieved 28 August 2015.
- ^ "LZ4 Compression". illumos. Archived from the original on 9 October 2018. Retrieved 28 August 2015.
- ^ Illumos #3035 LZ4 compression support in ZFS and GRUB on GitHub
- ^ "Features: lz4 compression". OpenZFS. Retrieved 28 August 2015.
- ^ Phillip Lougher (27 November 2014). "Squashfs: Add LZ4 compression configuration option". Retrieved 28 August 2015.
- ^ 7-zip-zstd
