Re: Slow Response for ASP.NET page

Jim,

That's very interesting information. I didn't realize the setting was at
the application pool level. This leaves me wondering (strictly curious, I
personally never use sessions), what happens to sessions that are set to
expire after the application pool recycle time?

E.g. Session Timeout = 60 (just hypothetical) & App pool recycle = 20

20 minutes go by, the app pool is recycled, 20 more minutes go by, (we're at
40 minutes since the last request), the user sends a request. What happens
now? The application is started up? This seems to indicate that since the
application went down any session state was lost. Seems like bad things
could happen because of this.

Am I missing something? Are we supposed to configure application pool
recycling to coinside with their application session timeouts? Ouch!

Ben

"JIMCO Software" <contactus@xxxxxxxxxxxxxxxxx> wrote in message
news:OOdTq$8rFHA.1256@xxxxxxxxxxxxxxxxxxxxxxx
> Lucas Tam wrote:
>>
>>> The server simply says, hey my last
>>> session has timed out, I'm not being used, so I'll shut down for
>>> memory conservations sake. I do think it would be cool to have a
>>> flag somewhere at the application level to indicate that you want to
>>> keep the application running at all times.
>>
>> Why not? Memory is cheap. Hardware is cheap. And if the administrator
>> wants the app to stay alive, what's wrong with that?
>
>
> Lucas,
>
> The problem here is that you've been given some false information.
> Depending on the OS, there are settings that control this.
>
> In IIS 5.0, the processModel element has an idleTimeout setting (defaults
> to infinite) that specifies how long the worker process can be idle (no
> requests) before it is shut down. If you're on IIS 5, check that.
>
> In IIS 6.0, the app pool has several settings that can cause the
> application to unload. On the Recycling tab, you can configure how the
> process is recycled. There is also a setting on the Performance tab that
> will recycle after 20 (default) minutes of inactivity. (This setting is
> the equivalent to the idleTimeout on IIS 5.
>
> The important point to remember is that what causes reJITting is when the
> application domain unloads. That causes the JITted assemblies to unload
> from the process. (Of course, the process shutting down causes the same
> issue.) Anytime the JITted assemblies are unloaded, you will have to
> incur the cost of JIT compilation again the next time the app is hit.
>
> --
> Jim Cheshire
> JIMCO Software
> http://www.jimcosoftware.com
>
> FrontPage add-ins for FrontPage 2000 - 2003
>
>
>
>


.

Relevant Pages

  • Re: IIS 6.0 Session expired with the following simple ASP lines?!?
    ... the session expires before the defined timeout if ... the application pool is recycling. ... I use this code to determine if the application is recycling: ... oh, btw, session and cookies are not the perfect way to work, write your own ...
    (microsoft.public.inetserver.iis)
  • Re: Session Timeout Problem
    ... and select the Application Pool in which your app runs. ... You don't say whether you tried using State Server. ... the loss of session variables due to Application/App Pool recycling. ... That usually works to prevent Session variable losses. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Buffer Pooling?
    ... >>If you need a buffer for each session, ... If I pool the state objects, ... > to put the state object back into the pool? ... The benefit of recycling them will be minimal. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Win2003 SP1 BSOD - STOP 0xab - DIAGNOSIS
    ... session unload. ... rdpdd.dll or a video driver. ... number of paged pool bytes that are leaking ... total number of paged and nonpaged allocations that are ...
    (microsoft.public.windows.server.general)
  • ASP.NET High memory usage
    ... We also grouped low level sites into 2 application pool. ... The main object is kept in session, and we also have some more tiny ... How can we measure the total session memory consumption for a worker ... Will it help us to have a session state server & web gardening? ...
    (microsoft.public.dotnet.framework.performance)