rapidgzip

Gzip Decompression and Random Access for Modern Multi-Core Machines

Runssource: GitHubApache-2.0commit d2350e9c9ba5

Apache-2.0 licensed. The project labels itself: cli, command line, command line tool, cpp, cpp17, cpp17 library, decompression and gzip.

rapidgzip runs. An Argusic agent installed it in 12 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

rapidgzip 0.16.0 installed in /tmp/venv, its CLI decompresses gzip input to byte-identical output, and its full test suite passes.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
475
forks
17
open issues
11
watchers
5
size
23 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing rapidgzip, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • source build failed: Python.h not found (no python3-dev, no root)3 minutes
  • test deps pytest/numpy/indexed_bzip2 missing2 minutes
  • PEP 668 blocked system pip install1 minute
  • pytest testGIL.py failed 2 tests without -X dev1 minute
  • unclosed RapidgzipFile aborts at interpreter exit with finalization message1 minute
Install time
12 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
rapidgzip --version printed 0.16.0; CLI decompress of GNU gzip matched input SHA-256 via cmp; python -X dev -u -m pytest librapidarchive/src/tests/testGIL.py exited 0 with 22 passed; testPythonWrappers.py exited 0 with 2240 cases
Model tokens used
216,215
Exact commit tested
d2350e9c9ba5
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **Launch/behavior**: `rapidgzip --version` printed `0.16.0`; CLI decompression of a GNU-gzip file…
- **Tests**: `testGIL.py` → `22 passed in 5.20s`; `testPythonWrappers.py` → exit 0 across 2240 para…
- **Errors recorded**: PEP 668 (venv), missing pytest/numpy/indexed_bzip2 deps (pip-installed), pyt…
Result line printed above as plain text.
tokens used
216,215
**Summary**
- **Install**: PEP 668 blocked system pip; I set up `/tmp/venv` and `pip install rapidgzip` succeed…
- **Launch/behavior**: `rapidgzip --version` printed `0.16.0`; CLI decompression of a GNU-gzip file…
- **Tests**: `testGIL.py` → `22 passed in 5.20s`; `testPythonWrappers.py` → exit 0 across 2240 para…
- **Errors recorded**: PEP 668 (venv), missing pytest/numpy/indexed_bzip2 deps (pip-installed), pyt…
Result line printed above as plain text.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Took 12 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 128 cli projects Argusic has installed and timed, rapidgzip was the 109th fastest to reach a running state, and 117 of 128 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

clicommand-linecommand-line-toolcppcpp17cpp17-librarydecompressiongzipgzip-decompressionheader-onlylibraryparallelpython-librarypython3random-accessthread

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/rapidgzip.svg)](https://argusic.com/subject/rapidgzip)

Questions

Does rapidgzip run?
Yes. rapidgzip runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test rapidgzip?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d2350e9c9ba5. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test rapidgzip?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does rapidgzip take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does rapidgzip need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing rapidgzip?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does rapidgzip compare with the alternatives?
Of the 128 cli projects Argusic has installed and timed, rapidgzip was the 109th fastest to reach a running state, and 117 of 128 reached one at all.
Where is the evidence for rapidgzip?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion