ASP.NET compilation timeout

[helveticus]

I noticed that the download time of my site has increased quite
dramatically over the last weeks. The ISP claims that my application
needs to be re-compiled every 30 minutes, which may explain the delay
after a certain period of inactivity.

I am aware that sessions will time out by default after 30 minutes. I
thought pages would compile whenever they are hit first but remain in
a compiled state afterward. Am I missing something? (ASP.NET 3.5) TIA.

[=?Utf-8?B?YnJ1Y2UgYmFya2Vy?=]

to free up server memory, there is also an idle time for a appdomain. your
isp proably has this set, so you cannot override it. if you are using inproc
sessions, your session can be lost if the session timeout is higher than the
idle timeout. so if no ones uses your site for the idle time (probably 30
minutes) your site appdoamin is unloaded (and all inproc session data lost).
the next page hit will cause a recompile/reload.
-- bruce (sqlwork.com)
"helveticus" wrote:

I noticed that the download time of my site has increased quite
dramatically over the last weeks. The ISP claims that my application
needs to be re-compiled every 30 minutes, which may explain the delay
after a certain period of inactivity.

I am aware that sessions will time out by default after 30 minutes. I
thought pages would compile whenever they are hit first but remain in
a compiled state afterward. Am I missing something? (ASP.NET 3.5) TIA.

[helveticus]

Thanks. I am aware of the fact that session timeouts can be overuled
by the ISP. Is the code really recompiled again if a page is hit after
a period of inactivity 30 min?