...
- bytes-written-rate [bytes/s]
- bytes-written-total [bytes]
- bytes-read-rate [bytes/s]
- bytes-read-total [bytes]
- bytes-flushed-rate [bytes/s]
- bytes-flushed-total [bytes]
- flush-time-(avg|min|max) [ms]
- memtable-hit-rate
- block-cache-data-hit-rate
- block-cache-index-hit-rate
- block-cache-filter-hit-rate
- bytes-read-compaction-rate [bytes/s]
- bytes-written-compaction-rate [bytes/s]
- compaction-time-(avg|min|max) [ms]
- write-stall-duration-(avg|total) [ms]
- num-open-files
- num-file-errors-total
...
A low memtable-hit-rate might indicate a too small memtable.
block-cache-data-hit-rate, block-cache-index-hit-rate, and block-cache-filter-hit-rate
If data is not found in the memtable, the block cache is consulted. This metric Metric block-cache-data-hit-rate measures the number of hits for data blocks with respect to the number of all lookups for data blocks into the block cache. The formula for this metric is the equivalent to the one for memtable-hit-rate.A low
Metrics block-cache-index-hit-rate and block-cache-datafilter-hit-rate measure the hit rates for index and filter blocks if they are cached in the block cache. By default index and filter blocks are cached outside of block cache. Users can configure RocksDB to include index and filter blocks into the block cache to better control the memory consumption of RocksDB. If users do not opt to cache index and filter blocks in the block cache, the value of these metrics should stay at zero.
A low hit-rate might indicate a too small block cache.
...
After data is flushed to disk, the data needs to be reorganised on disk from time to time. This reorganisation is called compaction and is performed by a background process. For the reorganisation, the data needs to be moved from disk to memory and back. Metrics bytes-read-compaction-rate and bytes-written-compaction-rate measure read and write throughput of compactions on average. Metrics compaction-time-(avg|min|max) measure the processing time of compactions.
...