Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TIDB 中tikv进程内存占用是否有有统一的试图或者监控来记录
[TiDB Usage Environment] Production Environment
[TiDB Version] v7.1.0
[Encountered Problem: Problem Phenomenon and Impact] Currently, from the monitor, we can only find the real memory usage of some TiKV components. There is no more detailed view available. Is there a simple way to obtain this information?
Not at the moment, let’s wait for future versions to improve. The tikv-detail monitoring has a memory trace that can show part of it, and then there’s the block cache in rocksdb.
I hope the product team can quickly implement the memory tracking feature for TiKV. I estimate that many customers need this, and many customers are already using hardware to handle the issue of increasing memory usage. 
Reduce the block cache size a bit.
This method has been used, but it hasn’t completely solved the problem. I happen to have another question: In writeCF, is there a way to see the space occupied by the index and the space occupied by MVCC?