This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Setup | |
These are from in-memory sysbench using 8 tables and 10M rows/table. | |
The test server has 56 HW threads with HT enabled. I look at the results for 24 concurrent clients, but I shared results for 1 to 64 clients. Numbers are QPS. | |
# Configs | |
cnf-1 has basic tuning | |
cnf-2 adds to cnf-1: | |
rocksdb_allow_concurrent_memtable_write=1 | |
rocksdb_enable_write_thread_adaptive_yield=1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Setup | |
For each test there are 3 runs. All use a build from May 8 (8may18). The first is write-committed (wcmt) and the next is with write-prepared (wprep). These are listed as myrocks.8may18.none.wcmt and myrocks.8may18.none.wprep. | |
The test server has 56 cores with HT enabled, 3 SSDs and 256gb of RAM. For the insert benchmark I use a table per client. Each table has a PK and 3 secondary indexes. | |
# Benchmark 1 | |
The first test is the insert benchmark load with 1 to 52 concurrent clients. 500m rows are inserted into N tables (table per client). Each insert transaction inserts 100 rows (~400 KV pairs given a PK and 3 secondary indexes). The insert rate is 7.8% better with write-prepared at 28 clients. | |
The first test is run 1, 2, 4, 8, ... 52 clients. The perf benefit from write-prepared starts at 8 clients. | |
-- 500m rows, n clients, n tables, in-memory | |
Average insert rate for 1 to 52 concurrent clients |