HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ckolivas
lrzip
C2017–2024
ckolivas / lrzip

lrzip

Long Range Zip

9Distinct people
9Mentions
0Explicit recommenders
708GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Long Range Zip

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2017-10-23 14:09:05 UTC to 2024-05-21 18:22:12 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC312
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

9 sources
Love this thing! It enabled me to add a “Convert to GIF” for videos in my Clop app (https://lowtechguys.com/clop) in just a few lines of code. The GIF gets encoded at its optimal size by default so I didn’t have to do a second optimization step. I also like that the author spent time to add an easy way to build a static binary, which I need in order to ship gifski inside the app. Compressing all these static binaries so I can ship them in Clop with a <100MB download was not so easy though. I’ve been using the included xz in macOS but I’m switching to lrzip [1] for better compression size and especially speed [1] https://github.com/ckolivas/lrzip
In Gifski: Optimized GIF Encoder
lrzip Long Range ZIP or LZMA RZIP https://github.com/ckolivas/lrzip "A compression utility that excels at compressing large files (usually > 10-50 MB). Larger files and/or more free RAM means that the utility will be able to more effectively compress your files (ie: faster / smaller size), especially if the filesize(s) exceed 100 MB. You can either choose to optimise for speed (fast compression / decompression) or size, but not both."
In How to get your backup to half of its size – ZSTD support
I typically don't make use of standard archive formats these days for my own file storage. If I want just pure maximum compression, I'll often use a long-range matcher like FreeArc's srep [1] or lrzip [2] combined with either fast-lzma2 [3] using a p7zip fork [4] for multithreading and fast compression or use mcm [5] or zpaq for max ratio with longer compression time. However, my truly preferred way is using dwarfs [6], which features some really good deduplication and (by default) zstd compression while being mountable. Most of my files are highly compressed and easily accessible without needing to full decompress them. I even made a small script to convert and create AppImages that instead use this [7]. Admittedly, I don't make use of PAR2 or anything of the sort, but I could just do that the traditional way if I so wished. [1]: https:/
Read the rest
In Don't Use RAR
Best I know of for that is something like lrzip still, but even then it's probably not state of the art. https://github.com/ckolivas/lrzip It'll also take a hell of a long time to do the compression and decompression. It'd probably be better to do some kind of chunking and deduplication instead of compression itself simply because I don't think you're ever going to have enough ram to store any kind of dictionary that would effectively handle so much data. You'd also not want to have to re-read and reconstruct that dictionary to get at some random image too.
In Ask HN: How would you store 10PB of data for your startup today?
The next default compressor might be lrzip [1] by Con Kolivas; I've only see it a couple of times in the wild so far but for certain files it can increase the compression ratio quite a bit. [1] https://github.com/ckolivas/lrzip # 151M linux-4.14-rc6.tar.gz # GZIP decompression ~$ time gzip -dk linux-4.14-rc6.tar.gz real 0m4.518s user 0m3.328s sys 0m13.422s # 787M linux-4.14-rc6.tar # LRZIP compression ~$ time lrzip -v linux-4.14-rc6.tar [...] linux-4.14-rc6.tar - Compression Ratio: 7.718. Average Compression Speed: 13.789MB/s. Total time: 00:00:56.37 real 0m56.533s user 5m35.484s sys 0m9.422s # 137M linux-4.14-rc6.tar.lrz # LRZIP decompression ~$ time lrzip -dv linux-4.14-rc6.tar.lrz [...] 100% 786.16 / 786.16 MB Average DeCompression Speed: 131.000MB/s Ou
Read the rest
tput filename is: linux-4.14-rc6.tar: [OK] - 824350720 bytes Total time: 00:00:06.35 real 0m6.524s user 0m8.031s sys 0m1.766s # Results ~$ du -hs linux* | sort -h 137M linux-4.14-rc6.tar.lrz 151M linux-4.14-rc6.tar.gz 787M linux-4.14-rc6.tar tested on WSL (Ubuntu BASH for Windows 10) edit: ~$ time xz -vk linux-4.14-rc6.tar linux-4.14-rc6.tar (1/1) 100 % 98.9 MiB / 786.2 MiB = 0.126 3.0 MiB/s 4:25 real 4m25.189s user 4m23.828s sys 0m1.094s ~$ du -hs linux* | sort -h 99M linux-4.14-rc6.tar.xz 137M linux-4.14-rc6.tar.lrz 151M linux-4.14-rc6.tar.gz 787M linux-4.14-rc6.tar It looks like XZ still has the best compression ratio but also took the longest (real)time.
In An ode to pack: gzip’s forgotten decompressor

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.