HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
powturbo
TurboBench
C++2015–2026
powturbo / TurboBench

TurboBench

Compression Benchmark

7Distinct people
29Mentions
0Explicit recommenders
377GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Compression Benchmark

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:04:15 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 year29 dated mentions

Observed mentions: 2015-11-25 12:39:35 UTC to 2026-09-16 11:56:01 UTC.

0510152015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 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): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC422
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
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 UTC303
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 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC13211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC321

What Hacker News says

13 sources
Sorry, a digit was missing, but now https://github.com/powturbo/TurboBench/issues/43 Well, a correct benchmarking is not done with special data, but with datasets that represent a large set of distributions. Such datasets are for ex. einwik8/9 for text, silesia for a mixed dataset. As a corner case example, RLE-compressible data is not representative for benchmarking compression libraries. If you provide a link for a dataset 10-100MB, I can verify your claims, because I'm not aware of a dataset where igzip is 2 times faster than libdeflate. In TurboBench there is no I/O or other overhead involved, additionally it's single threaded. It's also possible that you're comparing two different CLI programs, one (igzip) I/O optimized and the other as a simple CLI.
In Ebiggers/libdeflate: Heavily optimized DEFLATE/zlib/gzip library
I assume you wanted to link to TurboBench and not that particular issue, which for some reason also contains a link for some car listing? Secondly, did you not see my answer to ebiggers under this comment you replied to? Yes, for Silesia, libdeflate is faster, I can confirm, but there are at least two cases for which igzip is faster and one for which igzip is twice as fast. But yes, it heavily depends on the input data. Edit: I was then wondering why I could not find any igzip benchmarks on the repository's ReadMe and then found https://github.com/powturbo/TurboBench/issues/43 , so I guess this is the one you wanted to link to and the 3 got cut off.
In Ebiggers/libdeflate: Heavily optimized DEFLATE/zlib/gzip library
No, No and No. It's algorithmically impossible that zstd is decompressing faster than lz4 by using the same environment. You are comparing the zstd with asynchrounous I/O + multithreading against a single thread simple lz4 cli. Additionally you're using some exotic and not representative hardware. In theory, the only single thread decompression case where zstd can beats lz4 is when you have slow (reading) i/o. lz4 & zstd are mostly used as libraries and real benchmarks are not considering I/O or multithreading. This is what I'm getting with TurboBench & enwik9. lz4 decompressing 2,8x faster than zstd. C Size ratio% C MB/s D MB/s Name 356828015 35.7 400.71 1557.59 zstd 1 416874817 41.7 312.31 1967.66 lzav 509199084 50.9 630.78 4395.08 lz4 1 Dow
Read the rest
nload TurboBench [1] from [2] and make the tests on your machine. [1] - https://github.com/powturbo/TurboBench [2] - https://github.com/powturbo/TurboBench/releases
In LZAV – Fast In-Memory Data Compression Algorithm (In C)
LZAV now integrated into TurboBench [1] Download TurboBench for windows from releases [2] Lenovo IdeaPad 5 Pro - Ryzen 6600HS - DDR5 6400 - gcc-13.1 File: silesia.tar 220MB (Mixed text/binary) C Size ratio% C MB/s D MB/s Name 77885207 36.7 43.20 4479.24 lz4 9 81343184 38.4 123.17 4299.68 lz4 3 85664894 40.4 324.11 5171.12 lzturbo 11 88672448 41.8 435.96 2769.77 lzav v1.3 99553305 47.0 914.25 5425.54 lzturbo 10 100883728 47.6 813.76 4667.85 lz4 1 211948544 100.0 16032.92 16023.24 memcpy lzturbo (closed source) included as reference [1] https://github.com/powturbo/TurboBench [2] https://github.com/powturbo/TurboBench/releases
In LZAV – Fast In-Memory Data Compression Algorithm (In C)
I've made a benchmark with real html data including memory usage in [2] and a recent benchmark in [3] with TurboBench [1]. In the speedup plots you can see the best compressors for content providers: - brotli 11 is best for static content - brotli 5 is best until 1MB/s network transfer speed - libdeflate 6 is best from 1MB/s to 6MB/s (followed by brotli,4) - igzip 1,2 is best for very fast networks > 10MB/s brotli brings little value at decompression for users [1] https://github.com/powturbo/TurboBench [1] https://sites.google.com/site/powturbo/home/web-compression [2] https://encode.su/threads/2333-TurboBench-Back-to-the-future...
In A student’s desire to get out of a exam led to a compression algorithm

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.