C++ C Other
Failed to load latest commit information.
db clear warning about ~Version() not being virtual. Dec 16, 2016
doc merge google's 1.5 release Aug 28, 2012
helpers/memenv clean up redundant code to single RecoveryMmapSize() call. Add sugges… May 7, 2014
include/leveldb make expiry_ee inherit from expiry_os to create common code base. The… Nov 18, 2016
leveldb_ee @ dc9a1ec update leveldb_ee after adjustments per code review Nov 21, 2016
leveldb_os minor adjustments for compiling open source version. sst_scan use of … Nov 18, 2016
port Merge pull request #187 from basho/mv-expiry Jul 5, 2016
table address tab versus spaces issues within recent edits. Oct 10, 2016
tools comment out currently unused mod_time so compile works Dec 16, 2016
util make expiry_ee inherit from expiry_os to create common code base. The… Nov 18, 2016
.gitignore Lost gitignore entry of dSYM directories. Jan 5, 2016
.gitmodules restructure for Basho EE feature delivery Jan 16, 2016
.travis.yml Turn off travis support for submodules. travis will not have access t… Jan 16, 2016
AUTHORS reverting disastrous MOE commit, returning to r21 Apr 19, 2011
BASHO_RELEASES add comments for 2.0.33 tag Nov 21, 2016
LICENSE reverting disastrous MOE commit, returning to r21 Apr 19, 2011
Makefile Merge pull request #187 from basho/mv-expiry Jul 5, 2016
NEWS sync with upstream @ 21409451 May 21, 2011
README Update README Dec 16, 2014
README.GOOGLE Update README to be Basho specific and set write_buffer size default … Jun 27, 2013
TODO A number of smaller fixes and performance improvements: Jun 22, 2011
build_detect_platform Merge pull request #187 from basho/mv-expiry Jul 5, 2016


leveldb: A key-value store
Authors: Sanjay Ghemawat (sanjay@google.com) and Jeff Dean (jeff@google.com)

The original Google README is now README.GOOGLE.

** Introduction

This repository contains the Google source code as modified to benefit
the Riak environment.  The typical Riak environment has two attributes
that necessitate leveldb adjustments, both in options and code:

- production servers: Riak often runs in heavy Internet environments:
  servers with many CPU cores, lots of memory, and 24x7 disk activity.
  Basho's leveldb takes advantage of the environment by adding
  hardware CRC calculation, increasing Bloom filter accuracy, and
  defaulting to integrity checking enabled.

- multiple databases open: Riak opens 8 to 128 databases
  simultaneously.  Google's leveldb supports this, but its background
  compaction thread can fall behind.  leveldb will "stall" new user
  writes whenever the compaction thread gets too far behind.  Basho's
  leveldb modification include multiple thread blocks that each
  contain prioritized threads for specific compaction activities.

Details for Basho's customizations exist in the leveldb wiki:


** Branch pattern

This repository follows the Basho standard for branch management 
as of November 28, 2013.  The standard is found here:


In summary, the "develop" branch contains the most recently reviewed
engineering work.  The "master" branch contains the most recently
released work, i.e. distributed as part of a Riak release.

** Basic options needed

Those wishing to truly savor the benefits of Basho's modifications
need to initialize a new leveldb::Options structure similar to the
following before each call to leveldb::DB::Open:

    leveldb::Options * options;

    options=new Leveldb::Options;

    options.write_buffer_size=62914560;  // 60Mbytes
    options.total_leveldb_mem=2684354560; // 2.5Gbytes (details below)

** Memory plan

Basho's leveldb dramatically departed from Google's original internal
memory allotment plan with Riak 2.0.  Basho's leveldb uses a methodology
called flexcache.  The technical details are here:


The key points are:

- options.total_leveldb_mem is an allocation for the entire process,
  not a single database

- giving different values to options.total_leveldb_mem on subsequent Open
  calls causes memory to rearrange to current value across all databases

- recommended minimum for Basho's leveldb is 340Mbytes per database.  

- performance improves rapidly from 340Mbytes to 2.5Gbytes per database (3.0Gbytes
  if using Riak's active anti-entropy).  Even more is nice, but not as helpful.

- never assign more than 75% of available RAM to total_leveldb_mem.  There is
  too much unaccounted memory overhead (worse if you use tcmalloc library).

- options.max_open_files and options.block_cache should not be used.