It seems that in version 2.8, redis will no longer support the vm-enabled option. I guess the reason is for performance reasons. As the amount of data increases, it will report that there is insufficient memory, cannot be written, or even the server is down
Pay special attention when you are implementing a persistence strategy. For example, with 20G of memory, here comes the problem. When you insert data into redis, redis will asynchronously dump the data to the hard disk. It sounds perfect when you think about it. The problem is that it will fork a process and occupy the same size of memory. The memory you need is instantly 20G+20G =40G
I don’t know if your business volume is very large.
In addition, whether your business logic has memory leaks in the cache (resident cache). It is recommended to write a script to monitor the server memory usage. Sometimes it is difficult to find the problem just by looking at the redis log.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It seems that in version 2.8, redis will no longer support the vm-enabled option. I guess the reason is for performance reasons. As the amount of data increases, it will report that there is insufficient memory, cannot be written, or even the server is down
Pay special attention when you are implementing a persistence strategy.
For example, with 20G of memory, here comes the problem. When you insert data into redis, redis will asynchronously dump the data to the hard disk.
It sounds perfect when you think about it. The problem is that it will fork a process and occupy the same size of memory.
The memory you need is instantly 20G+20G =40G
I don’t know if your business volume is very large.
In addition, whether your business logic has memory leaks in the cache (resident cache).
I hope my suggestions can help youIt is recommended to write a script to monitor the server memory usage. Sometimes it is difficult to find the problem just by looking at the redis log.