GitHub user GoodManWEN added a comment to the discussion: How to configure row cache value to improve read performance?
Thank you @git-hulk . So actually it doesn’t matter what their allocation ratio is, as long as the total amount is the same, is that what it means? In the test I conducted a few days ago, I tested about 100 million keys of random data, and each value was about 16KB in length. I configured a total of 32GB maximum cache of 64GB for the above two items. During global random reading test, the memory usage has been maintained at around 8G, which I think is a relatively low level and makes me doubt whether the memory has been fully utilized (of course, the system cache has almost filled up all 64GB). According to the optimization suggestions I saw in on of the rocksdb tuning document before, it suggests setting the block cache to one-third of the physical memory and leaving the rest to the system cache. I am not sure if his wording refers to setting the upper limit in the setting item to one-third or whether one-third of physical memory should be occupied during actual operation. It would be very helpful if you could provide some additional explanations. GitHub link: https://github.com/apache/incubator-kvrocks/discussions/1353#discussioncomment-5424686 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
