MapInfo causes IIS application pool resources to run out. Another incorrect study note for IIS restart

Some time ago, I wrote ProgramMapInfo is used. Since it was just transferred to web development, and MapInfo was used for the first time, although this program was launched, it is always inaccessible because it is not often used, the general reason is that the application pool resources attached to the applications deployed in IIS are exhausted, and there is no good solution, so we take a relatively lazy behavior and restart IIS, and reclaim application pool resources, but it does not play a role. Later I realized that it was because I restarted the application in IIS, I thought he would initialize the entire server. The fact is that I was wrong. At six o'clock P.M. this afternoon, the customer encountered an inaccessible problem at the site. After being instructed by colleagues, they knew that they needed to restart the World Service (World)
Wide Web Publishing Service). After testing and restarting W3SVC, the problem is solved. Today, when I got off work, I learned a new knowledge about web development. I am very happy, although this knowledge may be well known.
In order to recycle the Mapinfo resources, I tried some methods to modify some settings of the application pool, and the results were not very satisfactory. Today, when I got off work, I wrote a Windows execution plan, restart the w3svc service at A.M. To Recycle resources. Create a BAT file and write two statements: net stop W3SVC and Net start w3svc. Program ---> attachment --> System Tool ---> execution plan --> Create an execution plan. Set the execution rules. If a problem occurs in the execution plan, refer to the official suggestions of MS for execution plan debugging.
The problem has been solved for the time being, but the problem is still being sought for answers. I hope you can give me more advice from our predecessors. Thank you.