Last year, an asp.net website used a large number of caches and restarted iis once in a few minutes. At that time, no reason was found. Some problems occurred during this period and it was suspected that the cache occupied too much memory, not verified
The descriptions are as follows:
If memory recycle is not enabled, IIS processes will use 1.3 GB of virtual memory and eventually stop responding. Then, an event is recorded similar to the following:
Event Type: Warning
Event Source: W3SVC
Event Type: None
Event ID: 1009:
Date:Date
Time:Time
User: N/
ComputerNameCOMPUTER:
Note:
The unexpected termination process provides the application pool DefaultAppPool. The process ID is "1234 ". The process exit code is "0 xc 0xc0000005 ".
For more information, see the Help and Support Center for the http://support.microsoft.com.
Link http://hi.baidu.com/ourok/blog/item/5353d30f6b64a0c27acbe177.html
Later, to avoid this problem, we used memcache to cache data, which was very stable and could be deployed in a distributed manner, improving availability.