You should try to instrument your app and check and see exactly what's taking up the time. Is it startup of the applicaiton? is it individual requests? Is it your SQL connection?

You can hookup Application_Start and Application_End to see if your app is being shut down frequently

+++ Rick ---




>>If you have an hour of idle time IIS will get released from memory. The default is 20 minutes. You can change that value in the Application Pool settings of IIS.
>>
>>Once loaded - regardless of length of time assuming it doesn't go beyond the application pool timeout, IIS is up and running and should respond fairly quickly. However, if your machine is memory strapped IIS may end up swapping to virtual memory if it's idle and that too can be slow - in fact slower than starting up the Application Pool again.
>>
>>if this is your dev box there's no reason to worry about this. If you have this problem you probably working on too low horsepower of a box. Even with an application pool startup even on my fairly old Core Duo laptop startup time from a cold start is no more than 10 seconds. Subsequent app pool restarts are more like 3-5 seconds on largish apps. If your's is taking significantly longer it's either your startup process that's slow (Application_Init code?) or your machine is really slow...
>
>Hi Rick
>
>Thanks for the reply, based on some more data of yesterday, when that happens, it happens after a period of 2 to 3 minutes. So, it is something out of the application pool default 20 minutes. When I looked at my Hit table, I saw that it took 5 to 6 seconds on that hit. So, basically, the application started to respond immediately but was slow to deliver the response. This seems to be something related to SQL Server. For some kind of reason, on that machine, if no activity is reported after 2 to 3 minutes, something takes longer on the next hit.