mirror of https://github.com/facebook/rocksdb.git
dfccc7b4e2
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 |
||
|---|---|---|
| .. | ||
| rdb | ||
| auto_sanity_test.sh | ||
| benchmark.sh | ||
| db_crashtest.py | ||
| db_crashtest2.py | ||
| db_repl_stress.cc | ||
| db_sanity_test.cc | ||
| db_stress.cc | ||
| dbench_monitor | ||
| ldb.cc | ||
| ldb_test.py | ||
| pflag | ||
| reduce_levels_test.cc | ||
| run_flash_bench.sh | ||
| sst_dump.cc | ||