haoyuhuang
bcfc53b436
Block cache tracing: Fix minor bugs with downsampling and some benchmark results. (#5473)
Summary:
As the code changes for block cache tracing are almost complete, I did a benchmark to compare the performance when block cache tracing is enabled/disabled.
With 1% downsampling ratio, the performance overhead of block cache tracing is negligible. When we trace all block accesses, the throughput drops by 6 folds with 16 threads issuing random reads and all reads are served in block cache.
Setup:
RocksDB: version 6.2
Date: Mon Jun 17 17:11:13 2019
CPU: 24 * Intel Core Processor (Skylake)
CPUCache: 16384 KB
Keys: 20 bytes each
Values: 100 bytes each (100 bytes after compression)
Entries: 10000000
Prefix: 20 bytes
Keys per prefix: 0
RawSize: 1144.4 MB (estimated)
FileSize: 1144.4 MB (estimated)
Write rate: 0 bytes/second
Read rate: 0 ops/second
Compression: NoCompression
Compression sampling rate: 0
Memtablerep: skip_list
Perf Level: 1
I ran the readrandom workload for 1 minute. Detailed throughput results: (ops/second)
Sample rate 0: no block cache tracing.
Sample rate 1: trace all block accesses.
Sample rate 100: trace accesses 1% blocks.
1 thread | | | -- | -- | -- | --
Sample rate | 0 | 1 | 100
1 MB block cache size | 13,094 | 13,166 | 13,341
10 GB block cache size | 202,243 | 188,677 | 229,182
16 threads | | | -- | -- | -- | --
Sample rate | 0 | 1 | 100
1 MB block cache size | 208,761 | 178,700 | 201,872
10 GB block cache size | 2,645,996 | 426,295 | 2,587,605
Pull Request resolved: https://github.com/facebook/rocksdb/pull/5473
Differential Revision: D15869479
Pulled By: HaoyuHuang
fbshipit-source-id: 7ae802abe84811281a6af8649f489887cd7c4618
2019-06-17 17:59:02 -07:00
..
2018-08-02 15:42:42 -07:00
2019-06-06 13:56:07 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2018-04-12 17:59:16 -07:00
2019-06-17 16:41:12 -07:00
2019-06-17 16:41:12 -07:00
2019-06-17 17:59:02 -07:00
2019-06-17 16:41:12 -07:00
2019-04-18 10:55:01 -07:00
2016-09-28 11:53:15 -07:00
2019-05-30 17:44:09 -07:00
2019-06-17 15:21:50 -07:00
2019-06-06 13:56:07 -07:00
2019-06-12 11:12:36 -07:00
2019-05-30 17:44:09 -07:00
2017-07-15 16:11:23 -07:00
2019-06-06 13:56:07 -07:00
2017-08-03 15:56:46 -07:00
2015-05-22 16:03:39 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2018-08-09 14:29:11 -07:00
2019-05-30 11:25:51 -07:00
2019-06-13 15:43:10 -07:00
2019-04-18 10:55:01 -07:00
2018-08-09 14:29:11 -07:00
2018-04-12 17:59:16 -07:00
2017-08-03 15:56:46 -07:00
2019-05-31 11:57:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2015-06-19 16:24:36 -07:00
2019-05-30 17:44:09 -07:00
2019-01-03 11:23:49 -08:00
2019-06-06 13:56:07 -07:00
2018-04-12 17:59:16 -07:00
2019-06-03 13:25:26 -07:00
2019-06-06 13:56:07 -07:00
2019-06-03 13:25:26 -07:00
2018-08-13 11:44:02 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-04-18 10:55:01 -07:00
2019-06-06 13:56:07 -07:00