Packages

rocksdb

0.22.0
3.1.1 3.1.0 3.0.0 2.6.2 2.6.1 retired 2.6.0 retired 2.5.0 2.4.1 2.4.0 2.3.0 2.2.0 2.1.0 2.0.0 1.9.0 1.8.0 1.7.0 1.6.0 1.5.1 1.5.0 1.4.0 1.3.2 1.3.1 1.3.0 1.2.0 1.1.1 1.1.0 1.0.0 0.26.2 0.26.1 0.26.0 0.25.0 0.24.0 0.23.3 0.23.2 0.23.1 0.23.0 0.22.0 0.21.0 0.20.1 0.20.0 0.19.0 0.18.0 0.17.0 0.16.0 0.15.0 0.14.0 0.13.1 0.13.0 0.12.0 0.11.0 0.10.0 0.9.1 0.9.0 0.8.2 0.8.1 0.8.0 0.7.1 0.7.0 0.6.4 0.6.3 0.6.2 0.6.1 0.6.0

RocksDB for Erlang

HexDocs

Current section

Files

Jump to
Readme
63 Versions
0 Dependencies
Dependants
Files
Activity
rocksdb deps rocksdb ROCKSDB_LITE.md
Raw

deps/rocksdb/ROCKSDB_LITE.md 

# RocksDBLite



RocksDBLite is a project focused on mobile use cases, which don't need a lot of fancy things we've built for server workloads and they are very sensitive to binary size. For that reason, we added a compile flag ROCKSDB_LITE that comments out a lot of the nonessential code and keeps the binary lean.



Some examples of the features disabled by ROCKSDB_LITE:

* compiled-in support for LDB tool

* No backupable DB

* No support for replication (which we provide in form of TransactionalIterator)

* No advanced monitoring tools

* No special-purpose memtables that are highly optimized for specific use cases

* No Transactions



When adding a new big feature to RocksDB, please add ROCKSDB_LITE compile guard if:

* Nobody from mobile really needs your feature,

* Your feature is adding a lot of weight to the binary.



Don't add ROCKSDB_LITE compile guard if:

* It would introduce a lot of code complexity. Compile guards make code harder to read. It's a trade-off.

* Your feature is not adding a lot of weight.



If unsure, ask. :)