Memory question

  • Thread starter Thread starter zdrakec
  • Start date Start date
Z

zdrakec

Hello all:

I have an aspx page which, when a remote machine opens it via IE, I see
a new entry in the Windows Task Manager on the server called w3wp.exe.
When I close the IE window on the remote machine that called up the Web
page, however, this process does not terminate.
Is there an explicit release of resources that I need to be doing in my
..aspx page that I am missing?

Thanks much,
zdrakec
 
No, w3wp is the worker process that starts on the first request. This
process will handle all incoming requests. When the requests quit coming
in, there is a timeout setting in IIS under the AppPool properties,
Performance tab.
"Shutdown worker process after being idle for:"

Set this to however long you want the process to hang around after the last
request has come in. If your site will be receving traffic, I would not set
this to too low of a value. The process really isn't taking up too much
resources when no requests are coming in, but you can tweak it all you want.

There is something else you said that is another whole discussion:
When I close the IE window on the remote machine that called up the Web
page, however, this process does not terminate.
Click to expand...

The server never, never knows about what the client has done with their
browser: closed it, gone to another site because your worker process kept
recycling and it took too long for your site to come up, etc.

There is some handy, crafty client side script you can implement for
receiving notification when a browser has closed, but I would never depend
on it, unless this is an internal application and your company has a
standard machine/build package.

bill
 
I wouldn't advise changing the value unless there is a good reason for it.
As the old saying goes "if it ain't fixed, don't broke it." ;-)

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
 
Back
Top