1560bb913e
Summary:
Added an option for readrandom benchmark to run with tailing iterator instead of Get. Benefit of tailing iterator is that it doesn't require locking DB mutex on access.
I also have some results when running on my machine. The results highly depend on number of cache shards. With our current benchmark setting of 4 table cache shards and 6 block cache shards, I don't see much improvements of using tailing iterator. In that case, we're probably seeing cache mutex contention.
Here are the results for different number of shards
cache shards tailing iterator get
6 1.38M 1.16M
10 1.58M 1.15M
As soon as we get rid of cache mutex contention, we're seeing big improvements in using tailing iterator vs. ordinary get.
Test Plan: ran regression test
Reviewers: dhruba, haobo, ljin, kailiu, sding
Reviewed By: haobo
CC: tnovak
Differential Revision: https://reviews.facebook.net/D15867
|
||
|---|---|---|
| .. | ||
| build_detect_platform | ||
| build_detect_version | ||
| fbcode.clang31.sh | ||
| fbcode.gcc471.sh | ||
| fbcode.gcc481.sh | ||
| format-diff.sh | ||
| mac-install-gflags.sh | ||
| make_new_version.sh | ||
| regression_build_test.sh | ||
| valgrind_test.sh | ||