You can configure the cache number of pages. When the maximum cache number is reached, the earliest page will be moved out of the memory. When rolling back, it will be judged whether it exists in the cache, and then it will be determined whether to read the cache or the server.
Basically don’t worry. Generally speaking, if you follow the official recommended writing method, you don’t need to worry about memory release. The framework will take care of these things. If you want to know more, you can take a look at closures and the automatic destruction mechanism of js.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
You can configure the cache number of pages. When the maximum cache number is reached, the earliest page will be moved out of the memory. When rolling back, it will be judged whether it exists in the cache, and then it will be determined whether to read the cache or the server.
Basically don’t worry. Generally speaking, if you follow the official recommended writing method, you don’t need to worry about memory release. The framework will take care of these things. If you want to know more, you can take a look at closures and the automatic destruction mechanism of js.
Yes, it mainly depends on how you write the code