Correct what a static rocksdb is good for
It said a static rocksdb is only needed for a completely static binary. What it
is actually good for is linking rocksdb and collocatordb statically into a
program, which needs no static zlib, snappy, lz4 and zstd - distributions like
Rocky Linux do not have those, and it does not matter.
Measured with rocksdb 7.8.3, which ships both variants: about 22% when counting
collocations and about 10% when looking them up.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Change-Id: If88dfe72104032a877bfd144879f5dc53c0f6dfb
diff --git a/README.md b/README.md
index aa13f5b..abb6c00 100644
--- a/README.md
+++ b/README.md
@@ -53,8 +53,13 @@
`libcollocatordb_static.a` is built as well. It is linked against the shared
rocksdb unless a static rocksdb is found, which is enough for most purposes.
-A static rocksdb is only needed to link a program completely statically, as
-dereko2vec does, which is worth about 10% on collocator lookups.
+
+Linking rocksdb and collocatordb statically into a program is worth about 22%
+when counting collocations and about 10% when looking them up, measured with
+rocksdb 7.8.3, which ships both variants. The compression libraries stay
+shared, so this does not need static versions of zlib, snappy and the others,
+which several distributions do not have. Only a completely static binary needs
+those, which is something else and rarely necessary.
Debian and Ubuntu ship `librocksdb.a` in `librocksdb-dev`, so there is nothing
to do. Fedora, Rocky Linux and RHEL do not ship one, so it has to be built.