GitHub user MarcoLugo added a comment to the discussion: Recommended configuration for large database?
Thank you @git-hulk . What I have observed so far is that with say, below 60GB of files, it uses all CPUs (32) to about 50-55% (with that being divided between normal threads and kernel threads) and I/O is high enough to be saturated. I should have mentioned, this is a read-intensive workload. Now, when above 100GB or so, for the same workload, CPU utilization in the same instance actually goes down and so does the I/O throughput and the database OPS and latency go down accordingly. I did try setting `rocksdb.block_cache_size` to 16384 and even to `32768` and saw no changes. I'll try again later to double check. GitHub link: https://github.com/apache/kvrocks/discussions/2673#discussioncomment-11321049 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
