I am using ASP.Net4 MVC2 for my application. The first person using the application usually experiences a long wait before the application responds. After that the applica
You need to accurately diagnose the problem first before you start implementation solutions. First have to verify if it is, in fact, an app pool recycle. You can start by adding this section to your web.config:
It will log an event to the windows event log anytime asp.net recycles itself. It will also gives a reason for the recycle (e.g., someone poked web.config, etc.). If it is a recycle, then you need to figure out why it is recycling. Is it because IIS is set to do it no matter what? Is it because your app is not handling memory correctly and memory pressure is causing asp.net to want to recycle itself? These questions must be answered first.
First determine if it is a recycle by adding to above configuration and why. Once you get the answer you can check memory, etc.