283a042969
Summary: This is done to avoid having each thread use the same seed between runs of db_bench. Without this we can inflate the OS filesystem cache hit rate on reads for read heavy tests and generally see the same key sequences get generated between teste runs. 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/D37563 |
||
---|---|---|
.. | ||
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 |