Skip to content

Fix docs: Snappy compressor works in 64 kB blocks instead of 32 kB now #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hwwhww wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix docs: Snappy compressor works in 64 kB blocks instead of 32 kB now #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions format_description.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
Snappy compressed format description
Last revised: 2011-10-05
Last revised: 2020-10-13


This is not a formal specification, but should suffice to explain most
Expand Down Expand Up @@ -76,9 +76,9 @@ yielding a form of run-length encoding (RLE). For instance,

<literal: "xab"> <copy: offset=2 length=4>

Note that since the current Snappy compressor works in 32 kB
Note that since the current Snappy compressor works in 64 kB
blocks and does not do matching across blocks, it will never produce
a bitstream with offsets larger than about 32768. However, the
a bitstream with offsets larger than about 65536. However, the
decompressor should not rely on this, as it may change in the future.

There are several different kinds of copy elements, depending on
Expand Down