Repository navigation
Docs and benchmarks for 1.1: single-session Silesia table, graphs, fuzz in CI - #7
Merged
Merged
Conversation
…, versions Silesia preset table re-measured on 1.1 with scripts/bench_session.py. The main run's opening sentinels read 26% slow, so -7, zpaq and -9 were re-run in a bracketed follow-up whose sentinels agree to 0.05% / 0.87%; the discarded rows stay in bench_session.json. Every preset is smaller than 1.0.2 (-0.2% to -2.4%), -9 whole-directory 35,467,098. -1 now beats lpaq1 on size, speed and memory; -5 still beats zpaq -m5 on all three. enwik8 ladder re-measured: 1.1 beats zpaq -m5 from -3 up (1.0.2: only -7 and -9). README, USAGE, dist/*.txt: tables, exchange rates, memory notes and derived claims regenerated from the data; graphs regenerated (mkgraphs, mkpresets, mkcorpora). bench_session.py gains --exe. scripts/wfuzz.py: round-trip fuzz for the word transform, which no other suite's inputs are large enough to reach; added to CI on Linux, macOS, Windows and under UBSan. SECURITY.md notes it and the -9 memory on text. Version strings: installer, sign script, CI fallback and dist headers to 1.1.0; README install guide no longer names a stale installer file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #6: brings the docs and benchmarks in line with 1.1.
Benchmarks
scripts/bench_session.py(one interleaved session, sentinels at both ends).-7, zpaq,-9) were measured under load.-7) and 0.87% (zpaq), and match the main run's closing readings.bench_session.jsonunderdiscarded.-9over the whole directory: 35,467,098.-1now beats lpaq1 on every axis: 0.90% smaller, 1.39× faster, 4 MB lighter.-5still beats zpaq -m5 on all three axes: 2.7% smaller, 1.75× faster, 43% less memory.-9is 1.18× zpaq's time here, against 1.07× in 1.0.2's session. A same-session A/B on mozilla (which the transform declines) shows 1.1 is 12% faster than 1.0.2 there, so this is session variance (§26), not the code. The docs say so.-3up; 1.0.2 only did at-7and-9.bench_session.pygains--exe.Docs
dist/*.txt: tables, marginal exchange rates, memory notes and every derived claim recomputed from the data.-7→-9is no worse than other steps" line is gone: in this session that step costs 19.4× per 1%, and the text now says so, with the cross-session caveat.Tests
scripts/wfuzz.py: round-trip fuzz for the word transform. None of the other suites' inputs reach it: they top out at 70 KB, and the transform starts at 256 KB.Versions