9da8748016
Summary: This changes loads to use vector memtable and disable the WAL. This also increases the chance we will see IO bottlenecks during loads which is good to stress test HW. But I also think it is a good way to load data quickly as this is a bulk operation and the WAL isn't needed. The two numbers below are the MB/sec rates for fillseq, bulkload using a skiplist or vector memtable and the WAL enabled or disabled. There is a big benefit from using the vector memtable and WAL disabled. Alas there is also a perf bug in the use of std::sort for ordered input when the vector is flushed. Task is open for that. 112, 66 - skiplist with wal 250, 116 - skiplist without wal 110, 108 - vector with wal 232, 370 - vector without wal 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/D36957 |
||
|---|---|---|
| .. | ||
| rdb | ||
| auto_sanity_test.sh | ||
| benchmark.sh | ||
| check_format_compatible.sh | ||
| db_crashtest2.py | ||
| db_crashtest.py | ||
| db_repl_stress.cc | ||
| db_sanity_test.cc | ||
| db_stress.cc | ||
| dbench_monitor | ||
| generate_random_db.sh | ||
| ldb_test.py | ||
| ldb.cc | ||
| pflag | ||
| reduce_levels_test.cc | ||
| run_flash_bench.sh | ||
| sst_dump.cc | ||
| verify_random_db.sh | ||