Worker process recycle question

  • Thread starter Thread starter John
  • Start date Start date
J

John

Is the only criteria for worker process recycle 60% physical memory usage??
(I'm on W2K, default setup - I know you can change it in machine.config).

Because if so, when using SQL Server on the same machine (knowing how memory
hungry it can be!) this presumably often inhibits recycling??

In the past I've had .NET 1.1 & SQL Server 2000 running on a 256Mb machine
(!!) with a very fat session state (in-proc storage), and no recycle
problems..

John
 
John,

There are a ton of reasons why the worker process might recycle.
Deadlocks, crashes, health recylcing, etc.

What do you see in the Event Viewer Application log?

Jim Cheshire [MSFT]
MCP+I, MCSE, MCSD, MCDBA
Microsoft Developer Support
(e-mail address removed)

This post is provided "AS-IS" with no warranties and confers no rights.


--------------------
 
no, there are several of causes for a recycle. too may recompiles, thread
failing to rundown, etc.

-- bruce (sqlwork.com)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Calling Application_Start After Worker Process is Recycled 6
does Session_End event fire when the worker process recycles? 1
session variables, Timeout and Recycling 5
Aspnet worker process recycling 6
Prevent worker process from recycling when foreground thread is executing. 3
IIS 6.0 Event 1074 6
How to minimize memory usage by asp.net application 3
A way to prove that StateServer is working? 2

Back
Top