linkedin / linkedin/migz

Windows Command-Line Tools

Open
#1 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
84
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Hi, could you provide binaries for Windows? Wanna include MiGz into my benchmark roster using 512KB and bigger blocks, by the way, how bigger they can be?

Your explanation of the acronym is not clear to me, please explain:
"... also supports multithreaded decompression, which is especially important for large files that are read repeatedly. Hence, MiGz."

What does the little 'i' stand for?

Allow me two more questions:
- Why not in C?
- Are you aware that MultIple decompressions are not bottlenecked by CPU in LzTurbo 29? I mean, your testresults using 4 cores are even inferior to the single-threaded decompression of LzTurbo 29/39!

```
1447249 12.6 0.50 471.90 brotli 11d29 ftp.gnu.org_grep-3.3.tar
1455165 12.6 2.10 137.62 lzma 9d29:fb273:mf=bt4 ftp.gnu.org_grep-3.3.tar
1489213 12.9 0.24 1063.22 oodle 139 ‘Leviathan’ ftp.gnu.org_grep-3.3.tar
1496718 13.0 0.18 1322.62 oodle 129 ‘Hydra’ ftp.gnu.org_grep-3.3.tar
1496718 13.0 0.45 1322.01 oodle 89 ‘Kraken’ ftp.gnu.org_grep-3.3.tar
1513749 13.1 2.24 1070.13 zstd 22d29 ftp.gnu.org_grep-3.3.tar
1517944 13.2 0.16 346.06 lzham 4fb258:x4:d29 ftp.gnu.org_grep-3.3.tar
1521395 13.2 1.49 1552.77 lzturbo 39 ftp.gnu.org_grep-3.3.tar
1756302 15.2 39.10 1542.17 lzturbo 32 ftp.gnu.org_grep-3.3.tar
1774686 15.4 21.85 1145.93 zstd 12 ftp.gnu.org_grep-3.3.tar
1782164 15.5 1.52 1953.87 lzturbo 29 ftp.gnu.org_grep-3.3.tar
1875468 16.3 1.47 1581.11 lizard 49 ftp.gnu.org_grep-3.3.tar
2114046 18.4 54.64 886.77 oodle 132 ‘Leviathan’ ftp.gnu.org_grep-3.3.tar
2163309 1548 Nakamichi 'Ryuugan-ditto-1TB' ! Outside TurboBench, Intel-v15.0-64bit-archSSE41 compile !
2172516 18.9 2.42 3501.52 oodle 118 ‘Selkie’ ftp.gnu.org_grep-3.3.tar
2172516 18.9 2.42 3495.15 oodle 116 ‘Selkie’ ftp.gnu.org_grep-3.3.tar
2359093 20.5 306.55 1233.67 lzturbo 30 ftp.gnu.org_grep-3.3.tar
2404889 20.9 15.35 333.83 zlib 9 ftp.gnu.org_grep-3.3.tar
2406525 20.9 46.42 3756.11 oodle 114 ‘Selkie’ ftp.gnu.org_grep-3.3.tar

```
As you can see from the above (random) test, LzTurbo 30 decompresses 1233.67/333.83=3.69x and compresses 306.55/15.35=19.97x faster than zlib 9!

```
6998037 17.4 0.90 849.88 lzturbo 39 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
7022279 17.4 0.37 321.86 brotli 11d29 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
7049563 17.5 1.38 684.89 zstd 22d29 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
7071491 17.5 0.29 644.84 oodle 139 ‘Leviathan’ Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
7103502 17.6 0.40 724.20 oodle 89 ‘Kraken’ Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
7105986 17.6 0.23 723.98 oodle 129 ‘Hydra’ Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
7125187 17.7 10.61 25.82 bzip2 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
7960854 19.8 0.91 1302.16 lzturbo 29 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
8061825 20.0 1.38 924.79 lizard 49 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
9041702 1077 Nakamichi 'Ryuugan-ditto-1TB' ! Outside TurboBench, Intel-v15.0-64bit-archSSE41 compile !
9314676 23.1 37.27 1085.78 lzturbo 32 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
9759547 24.2 0.57 1812.03 oodle 116 ‘Selkie’ Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
9759547 24.2 0.57 1810.97 oodle 118 ‘Selkie’ Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
10771358 26.7 4.30 320.47 zlib 9 Complete_works_of_Fyodor_Dostoyevsky_in_15_volumes_(Russian).tar
```
For the second random example, LzTurbo 29 is 4x faster than zlib 9 in decompression, no need of 4 cores.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The request concerns Windows binaries for MiGz's command-line utilities, along with explanations of the acronym, block sizes, language choice, and benchmark results. Start by reviewing how the platform-independent Java library and command-line utilities are packaged; done would require a defined Windows distribution and resolved documentation questions, but the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.