Mark Callaghan dfccc7b4e2 Add readwhilemerging benchmark ... Summary: This is like readwhilewriting but uses Merge rather than Put in the writer thread. I am using it for in-progress benchmarks. I don't think the other benchmarks for Merge cover this behavior. The purpose for this test is to measure read performance when readers might have to merge results. This will also benefit from work-in-progress to add skewed key generation. Task ID: # Blame Rev: Test Plan: Revert Plan: Database Impact: Memcache Impact: Other Notes: EImportant: - begin *PUBLIC* platform impact section - Bugzilla: # - end platform impact - Reviewers: igor Reviewed By: igor Subscribers: dhruba Differential Revision: https://reviews.facebook.net/D35115		2015-03-18 13:50:52 -07:00
..
rdb
auto_sanity_test.sh
benchmark.sh	Add readwhilemerging benchmark	2015-03-18 13:50:52 -07:00
db_crashtest.py
db_crashtest2.py
db_repl_stress.cc
db_sanity_test.cc	rocksdb: Add missing override	2015-02-26 11:28:41 -08:00
db_stress.cc	rocksdb: Fixed 'Dead assignment' and 'Dead initialization' scan-build warnings	2015-02-23 14:10:09 -08:00
dbench_monitor	Added simple monitoring script to monitor overusage of memory in db_bench	2015-02-11 18:40:11 -08:00
ldb.cc
ldb_test.py
pflag	Added simple monitoring script to monitor overusage of memory in db_bench	2015-02-11 18:40:11 -08:00
reduce_levels_test.cc	rocksdb: switch to gtest	2015-03-17 14:08:00 -07:00
run_flash_bench.sh
sst_dump.cc