I have web application on IIS6 Win2003. This application connected to w3wp.exe process which reaches 50-70% of CPU after 3-4 minutes it was recycled ( forced one ). I have few places with Cache in this project so my questions concern the case if i set AppPool recycle limits and the process will recycle every few minutes to avoid high CPU overload unless i find what causing it which can take years ( heh )…
There are two types of Cache i’m using though the Web Application project, Output Cache and Cache.
What happens to two of those once i recycle application?
In case two of those deleted what should i do in order to keep those alive even if i recycle Application Pool ?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
The Cache is part of the application domain so recycling the Application Pool will invalidate all cache items.
This will also happen if you modify the web.config file or the bin folder.
Method 2
you could look at out of process caching, that will survive app-pool restart and could be shared in a multi-node applications,
Have a look at Velocity (Microsoft AppFabric) or SharedCache (Opensource)
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0