Aspnet worker process recycling

[mark]

Just wondering if anyone has aspnet process recycling set up in any
production environments. Our worker process memory gets out of control
after being up for about a day or so and we were thinking about setting up
some thresholds on memory usage.

Any experiences using this would be greatly appreciated.

thanks

 

[Curt_C [MVP]]

what do you need to know? I believe I have one site set to with something
like a 100mb limit threshhold (might be lower/higher, dont remember).
Setting it up is no biggie, just dont set it too low to kill your site.

 

[mark]

Just wondering if it caused any problems. Like killing sessions or messing
up a request if it was in the middle of processing a page when it restarts.

thanks

 

[ashelley]

Just wondering if it caused any problems. Like killing sessions or messing
up a request if it was in the middle of processing a page when it restarts.

thanks

I believe the sessions will be lost.

-Adam

 

[Curt_C [MVP]]

Yup. That it can/will.
But then again, if it spikes that high/hard your sessions are probably going
to timeout anyway. Better to recycle that app pool then recycle the entire
server's pools.

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com

 

[mark]

That's weird because we've been testing this internally by setting the
timeout to 1 MINUTE, and then pounding pages that all use session and they
work fine. If the session was lost, the page would error.

?

 

[mark]

Oh, I think why we don't lose session state is because we're using an actual
state server, so our state is not stored in the aspnet worker process.

thanks.

http://www.eggheadcafe.com/articles/20021016.asp