llama-zip is a lossless compression utility that leverages a user-provided LLM (large language model) as the probabilistic model for an arithmetic coder. This allows llama-zip to achieve high compression ratios on structured or natural language text, since few bits are needed to encode tokens that the model predicts with high confidence. By employing a sliding context window, llama-zip is not limited by the context length of the LLM and can compress strings of arbitrary length. Furthermore, by encoding invalid UTF-8 bytes using code points in Unicode's private use areas, llama-zip is not limited to text inputs and can handle arbitrary binary data, albeit with reduced compression ratios compared to text inputs.
In the table below, the compression ratios achieved by llama-zip on the text files of the Calgary Corpus (as well as on llama-zip's own source code, llama_zip.py) are compared with other popular or high-performance compression utilities. Compression ratios are calculated by dividing the number of bytes in the uncompressed input by the number of bytes in the compressed output, so higher values indicate more effective compression.
For llama-zip, two LLMs were benchmarked at two context lengths, with a consistent window overlap of 25% (see Options for more info):
- Phi-3.1-mini-128k-instruct (Q4_K_M)
- 8192-token context length ("phi-8k" in the table)
- 32768-token context length ("phi-32k" in the table)
- Llama-3.1-8B (Q4_K_M)
- 8192-token context length ("llama-8k" in the table)
- 32768-token context length ("llama-32k" in the table)
For the other utilities, the maximum compression level offered was used.
| File | llama‑zip (llama‑8k) | llama‑zip (llama‑32k) | llama‑zip (phi‑32k) | llama‑zip (phi‑8k) | cmix | paq8px | paq8pxd | zpaq | brotli | bzip2 | lzma | xz | zstd | gzip |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bib | 15.001 | 13.577 | 10.473 | 9.920 | 5.633 | 5.668 | 5.590 | 4.611 | 3.920 | 4.051 | 3.641 | 3.636 | 3.485 | 3.171 |
| book1 | 8.745 | 8.278 | 7.087 | 6.997 | 4.209 | 4.192 | 4.204 | 3.823 | 2.999 | 3.305 | 2.942 | 2.941 | 2.904 | 2.460 |
| book2 | 12.250 | 11.852 | 10.682 | 10.108 | 5.381 | 5.346 | 5.325 | 4.649 | 3.696 | 3.880 | 3.598 | 3.596 | 3.514 | 2.963 |
| news | 9.976 | 9.350 | 8.395 | 7.935 | 4.542 | 4.531 | 4.494 | 3.817 | 3.338 | 3.180 | 3.173 | 3.171 | 3.073 | 2.610 |
| paper1 | 12.577 | 12.869 | 10.442 | 10.072 | 4.264 | 4.302 | 4.212 | 3.572 | 3.439 | 3.211 | 3.083 | 3.074 | 3.017 | 2.867 |
| paper2 | 12.370 | 12.460 | 10.787 | 10.561 | 4.180 | 4.208 | 4.135 | 3.679 | 3.308 | 3.283 | 3.020 | 3.015 | 2.982 | 2.769 |
| progc | 13.802 | 14.002 | 10.714 | 10.188 | 4.439 | 4.438 | 4.352 | 3.495 | 3.409 | 3.158 | 3.162 | 3.151 | 3.096 | 2.968 |
| progl | 20.429 | 20.228 | 14.733 | 14.054 | 7.497 | 7.464 | 7.347 | 5.554 | 5.116 | 4.599 | 4.801 | 4.787 | 4.728 | 4.432 |
| progp | 20.438 | 21.888 | 16.722 | 15.450 | 7.705 | 7.665 | 7.508 | 5.348 | 4.998 | 4.611 | 4.792 | 4.772 | 4.724 | 4.414 |
| trans | 12.523 | 13.497 | 11.746 | 9.776 | 8.650 | 8.484 | 8.409 | 6.597 | 6.083 | 5.235 | 5.628 | 5.613 | 5.417 | 4.949 |
| llama_zip.py | 29.083 | 29.083 | 23.383 | 23.383 | 4.904 | 4.976 | 4.689 | 3.018 | 3.980 | 3.508 | 3.608 | 3.552 | 3.633 | 3.542 |
The best-performing compressor for each file is listed in bold, and the second-best is underlined. The columns are sorted by average compression ratio achieved across all files, with overall better-performing compressors listed further to the left.
These results show that llama-zip can significantly outperform traditional compression utilities, at least with the LLMs and files tested. Note that increased context length might not lead to better compression ratios past a certain point, though, as evidenced by the fact that Llama 3.1 performed better on average with an 8k-token context length than with a 32k-token context length. Context lengths longer than 32k tokens were not tested due to memory and time constraints.
git clone https://github.com/alexbuz/llama-zip.git
cd llama-zip
pip3 install .To use llama-zip, you must download an LLM that is compatible with llama.cpp, such as Llama 3.1 8B. Make sure to download a quantized version (one of the .gguf files listed on the "Files and versions" tab on Hugging Face) that is small enough to fit in your system's memory.
llama-zip <llm_path> [options] <mode> [input]
llama-zip supports three modes of operation:
- Compress mode (specified by the
-cor--compressflag): The string to be compressed can be provided as an argument or piped to stdin. The compressed output will be written to stdout. - Decompress mode (specified by the
-dor--decompressflag): The compressed string can be provided as an argument or piped to stdin. The decompressed output will be written to stdout. - Interactive mode (specified by the
-ior--interactiveflag): A prompt is displayed where the user can enter strings to be compressed or decompressed. When a base64-encoded string is entered, it will be treated as representing compressed data and will be decompressed; otherwise, it will be compressed. After each compression or decompression operation, the user is prompted to enter another string. To exit interactive mode, pressCtrl+C.- Note: If you would like to compress a string that consists entirely of base64 characters (i.e., letters, numbers,
+, and/, without any other symbols or spaces), you must use compression mode directly, as interactive mode assumes that base64-encoded strings are meant to be decompressed and will result in nonsensical output if the input did not come from a compression operation. Alternatively, you can add a non-base64 character to your string (such as a space at the end) if you don't mind that character being compressed along with the rest of the string.
- Note: If you would like to compress a string that consists entirely of base64 characters (i.e., letters, numbers,
-f,--compressed-format: The format of compressed data. This can be set tobinary(the default for non-interactive modes) orbase64(the default and only supported format for interactive mode).-w,--window-overlap: The number of tokens to overlap between the end of the previous context window and the start of the next window, when compressing a string whose length exceeds the model's maximum context length. This can be specified as a percentage of the model's context length or as a fixed number of tokens. The default is0%, meaning that the context window is cleared entirely when it is filled. Higher values can improve compression ratios but will slow down compression and decompression. Note that when decompressing, the window overlap must be set to the same value that was used during compression in order to reconstruct the original string.--n-ctx: The number of tokens to use as the context length for the model. This must be less than or equal to the model's maximum context length. If set to0(the default), then the model's maximum context length will be used. Note that when decompressing, the context length must be set to the same value that was used during compression in order to reconstruct the original string.--n-gpu-layers: The number of model layers to offload to the GPU. This can significantly speed up compression and decompression, especially for larger models. If set to-1(the default), then all layers will be offloaded. See the llama.cpp repository for more information. In practice, the same number of layers should be offloaded during compression and decompression.--use-mlock: Force your system to keep the entire model in memory. This can be useful for larger models but may cause your system to run out of memory if the model is too large. Disabled by default.
-
Compress a file:
llama-zip /path/to/llm.gguf -c < input.txt > compressed.llzp
-
Compress a string and print the compressed output in base64 format:
llama-zip /path/to/llm.gguf -f base64 -c "The quick brown fox jumps over the lazy dog."
-
Decompress a file:
llama-zip /path/to/llm.gguf -d < compressed.llzp > output.txt
-
Decompress a base64-encoded compressed string:
llama-zip /path/to/llm.gguf -f base64 -d BASE64_STRING
- Start an interactive mode session:
llama-zip /path/to/llm.gguf -i
The LlamaZip class can be used to compress and decompress data programmatically. The compress method takes a bytes object and returns a another bytes object containing the compressed data. The decompress method takes a bytes object containing compressed data and returns the original uncompressed data.
from llama_zip import LlamaZip
# Initialize the compressor
compressor = LlamaZip(model_path="/path/to/model.gguf")
# Compress some data
original = b"The quick brown fox jumps over the lazy dog."
compressed = compressor.compress(original)
assert len(compressed) < len(original)
# Decompress the data
decompressed = compressor.decompress(compressed)
assert decompressed == originalThe LlamaZip constructor also accepts the n_ctx, n_gpu_layers, and use_mlock arguments, which correspond to the CLI options of the same names. The window_overlap argument can be passed to the compress and decompress methods directly to specify the window overlap for that particular operation.
- Speed: Compression and decompression speeds are limited by the speed of LLM inference. This renders llama-zip significantly slower than traditional compression utilities. However, the compression ratios achieved by llama-zip may justify the trade-off in speed for certain use cases.
- Portability: llama-zip requires identical LLM behavior during compression and decompression. However, the backend that llama-zip uses for LLM inference, llama.cpp, does not currently guarantee deterministic behavior. This limits the portability of the compressed output of llama-zip, as it may not be decompressible on a different system, even if the same model is used. In practice, behavior also differs depending on the number of GPU layers offloaded, so the
--n-gpu-layersoption should be set to the same value during compression and decompression, in addition to the window overlap (--window-overlap) and context length (--n-ctx) options. - Binary Compression: Due to its reliance on an LLM for prediction, llama-zip is best suited for compressing inputs that consist primarily of text. Although llama-zip can handle binary data by encoding invalid UTF-8 bytes using code points in Unicode's private use areas, it may not achieve high compression ratios on such data, potentially producing compressed output that is larger than the original input.