Find a file
2019-11-05 11:08:10 -08:00
arcanist_util
build_tools [FB Internal] Point to the latest tool chain. 2019-10-31 14:12:34 -07:00
cmake/modules
coverage
db Reset DBIter::saved_key_ with proper user key anywhere before pass to DBIter::FindNextUserEntry 2017-03-08 17:41:09 -08:00
docs
examples
hdfs
include/rocksdb Bump version to 5.1.5 2017-03-08 17:45:02 -08:00
java
memtable
port change UseDirectIO() to use_direct_io() 2017-01-13 12:09:15 -08:00
table Revert "PinnableSlice" 2017-01-08 14:24:12 -08:00
third-party
tools Revert "PinnableSlice" 2017-01-08 14:24:12 -08:00
util Make compaction_pri settable through option string 2017-03-02 14:58:29 -08:00
utilities Fix for 2PC causing WAL to grow too large 2017-01-20 10:46:47 -08:00
.arcconfig
.clang-format
.gitignore
.travis.yml travis: For linux, do all tests under gcc 2017-01-13 15:39:13 -08:00
appveyor.yml
AUTHORS
CMakeLists.txt
CONTRIBUTING.md
DEFAULT_OPTIONS_HISTORY.md
DUMP_FORMAT.md
HISTORY.md Update HISTORY.md for wrong release date 2017-02-08 11:28:31 -08:00
INSTALL.md
LANGUAGE-BINDINGS.md
LICENSE
Makefile Disable warning as error 2019-11-05 11:08:10 -08:00
PATENTS
README.md
ROCKSDB_LITE.md
src.mk
thirdparty.inc
USERS.md
Vagrantfile
WINDOWS_PORT.md

RocksDB: A Persistent Key-Value Store for Flash and RAM Storage

Build Status Build status

RocksDB is developed and maintained by Facebook Database Engineering Team. It is built on earlier work on LevelDB by Sanjay Ghemawat (sanjay@google.com) and Jeff Dean (jeff@google.com)

This code is a library that forms the core building block for a fast key value server, especially suited for storing data on flash drives. It has a Log-Structured-Merge-Database (LSM) design with flexible tradeoffs between Write-Amplification-Factor (WAF), Read-Amplification-Factor (RAF) and Space-Amplification-Factor (SAF). It has multi-threaded compactions, making it specially suitable for storing multiple terabytes of data in a single database.

Start with example usage here: https://github.com/facebook/rocksdb/tree/master/examples

See the github wiki for more explanation.

The public interface is in include/. Callers should not include or rely on the details of any other header files in this package. Those internal APIs may be changed without warning.

Design discussions are conducted in https://www.facebook.com/groups/rocksdb.dev/