# Other Reasons

+ High memory consumption during raftstore data write


![left](./student-guide/diagram/24-Other-reasons-01-01.png)

+ Target server has a mix of other components and high memory consumption 

------------------------------------------------------------

- High memory consumption for raftstore data writing
In terms of memory consumption, apart from block-cache, raftstore channels and messages in apply channels all occupy memory to a certain extent.
For v4.0 and v5.0 versions, there is no intuitive monitoring to see detailed consumption information of TiKV memory. Relevant monitoring items need to be written in conjunction with TIKV-details, such as Apply log duration, Performed wait duration and other monitoring items to assist judgment. Starting with the v5.1 version, a Memory trace item has been added to the TikV-Details —> Server, which can be displayed at a more granular level, the memory occupied by each thread in the raftstore:

- Target server has a mix of other components and high memory consumption
The server where TiKV is located is mixed with many other application components that take up too much memory and may also lead to the possibility of TiKV being oom-killer by the operating system.