dolysis/rocksdb
3
0
Fork 0
mirror of https://github.com/facebook/rocksdb.git synced 2024-11-30 04:41:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
1785 commits 196 branches 277 tags 394 MiB
C++ 84.3%
Java 9.6%
C 1.6%
Python 1.5%
Perl 0.9%
Other 2%
Find a file
Igor Canadi 8cb7ad83c3 Flush stale column families less aggressively 
Summary:
We've seen some production issues where column family is detected as stale, although there is only one column family in the system. This is a quick fix that:
1) doesn't flush stale column families if there's only one of them
2) Use 4 as a coefficient instead of 2 for determening when a column family is stale. This will make flushing less aggressive, while still keep a nice dynamic flushing of very stale CFs.

Test Plan: make check

Reviewers: dhruba, haobo, ljin, sdong

Reviewed By: sdong

Subscribers: leveldb

Differential Revision: https://reviews.facebook.net/D18861
2014-06-02 15:33:54 -07:00
build_tools hdfs cleanup and compile test against CDH 4.4. 2014-05-20 17:22:12 -04:00
coverage Disable the html-based coverage report by default 2014-02-06 12:58:13 -08:00
db Flush stale column families less aggressively 2014-06-02 15:33:54 -07:00
doc doc: table_stats_collectors -> table_properties_collectors. 2014-02-07 12:19:25 -08:00
examples Make it easier to start using RocksDB 2014-05-10 10:49:33 -07:00
hdfs hdfs cleanup and compile test against CDH 4.4. 2014-05-20 17:22:12 -04:00
helpers/memenv Expose in memory Env to the world 2014-04-14 12:28:15 -07:00
include Move master version to 3.2 2014-05-23 10:27:56 -07:00
java [Java] Generalize dis-own native handle and refine dispose framework. 2014-05-28 18:16:29 -07:00
linters allow lambda function syntax in cpplint 2014-02-20 12:47:05 -08:00
port Make rocksdb work with all versions of lz4 2014-05-05 11:35:40 -07:00
table forward iterator 2014-05-30 14:31:55 -07:00
third-party/rapidjson Add rapidjson to RocksDB 2014-05-15 16:07:05 -07:00
tools db_stress to add an option to periodically change background thread pool size. 2014-06-02 10:32:09 -07:00
util ThreadID printed when Thread terminating in the same format as posix_logger 2014-05-29 11:11:08 -07:00
utilities Make RateLimiting unit test less flakey 2014-05-20 17:09:38 -07:00
.arcconfig Improve/fix bugs for the cpp linter 2014-02-13 17:48:11 -08:00
.clang-format A script that automatically reformat affected lines 2014-01-14 12:21:24 -08:00
.gitignore Add .swp to gitignore 2014-05-16 13:17:29 -07:00
.travis.yml Turn off travis notifications 2014-05-14 16:08:02 -07:00
CONTRIBUTING.md New CLA form 2014-04-22 09:12:19 -07:00
HISTORY.md Update HISTORY.md 2014-05-21 15:25:05 -07:00
INSTALL.md Better INSTALL.md and Makefile rules 2014-05-07 16:51:30 -07:00
LICENSE Fix copyright year 2014-03-12 12:06:58 -07:00
Makefile Move master version to 3.2 2014-05-23 10:27:56 -07:00
PATENTS Fix the patent format 2013-10-16 15:37:32 -07:00
README.md Add build status to README.md 2014-05-15 10:16:58 -07:00
ROCKSDB_LITE.md RocksDBLite 2014-04-15 13:39:26 -07:00

README.md

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

Build Status

RocksDB is developed and maintained by Facebook Database Engineering Team. It is built on 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 an 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 doc/index.html and 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/