w3wp process

I am using windows 2003.

I have unchecked all options in IIS6 application pool,
so I assume no worker process recycling will be performed whether any event
occured.

what will be happened when w3wp.exe used memory exceed physical memory.

outofmemory throw and then recycle?

any idea?Hi Ricky:

This is a bit risky. A process can allocate more memory than
physically exists in the machine thanks to Windows virtual memory
management. Some portions of allocated memory can move to disk and
back.

As you get close to exhausting virtual memory the system can slow down
tremendously. Some of this is due to hard disk 'thrashing' as Windows
has to use the disk to supplement physical memory, but also because
memory allocations begin to fail and more and more error code and
exception handling code is executed. Your server might melt down
before a process stops and recycles.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Sun, 10 Jul 2005 20:51:01 -0700, "Ricky Chan"
<RickyChan@.discussions.microsoft.com> wrote:

>I am using windows 2003.
>I have unchecked all options in IIS6 application pool,
>so I assume no worker process recycling will be performed whether any event
>occured.
>what will be happened when w3wp.exe used memory exceed physical memory.
>outofmemory throw and then recycle?
>any idea?
>
Thank you.
One More question,
If there is VM managament, why outofmemory exception throw out?

I have searched many post, it seems the process will be recycled
after outofmemory exception throw.
I have tested it (development), the process w3wp doesn't recycle, but
release the memory
immediately.(same pid)

In the production environment, the process is dead after outofmemory exception
throw. I need to use the IISreset to resume the service.

Any idea?
thank you so much.

"Scott Allen" wrote:

> Hi Ricky:
> This is a bit risky. A process can allocate more memory than
> physically exists in the machine thanks to Windows virtual memory
> management. Some portions of allocated memory can move to disk and
> back.
> As you get close to exhausting virtual memory the system can slow down
> tremendously. Some of this is due to hard disk 'thrashing' as Windows
> has to use the disk to supplement physical memory, but also because
> memory allocations begin to fail and more and more error code and
> exception handling code is executed. Your server might melt down
> before a process stops and recycles.
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
> On Sun, 10 Jul 2005 20:51:01 -0700, "Ricky Chan"
> <RickyChan@.discussions.microsoft.com> wrote:
> >I am using windows 2003.
> >I have unchecked all options in IIS6 application pool,
> >so I assume no worker process recycling will be performed whether any event
> >occured.
> >what will be happened when w3wp.exe used memory exceed physical memory.
> >outofmemory throw and then recycle?
> >any idea?
>
I m using windows 2003 and .Net Framewokr1.1 and using iis6
i m frequently get the error of "system.outofmemoryException was thrown"

From http://www.developmentnow.com/g/8_2...3wp-process.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com