Re: IIS memory issue
From: Pat [MSFT] (patfilot_at_online.microsoft.com)
Date: 12/18/04
- Next message: Pat [MSFT]: "Re: 2003 Server, quad proc, IIS box - CPU @100%"
- Previous message: Pat [MSFT]: "Re: IIS State Log Analysis"
- In reply to: lan: "IIS memory issue"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Dec 2004 18:10:07 -0800
Virtual Memory Allocated refers to the 2GB virtual memory map. So, when you
load a dll (i.e. instantiate a COM object for the first time), this value
will increase. If a Heap segment is extended, it will increase, etc.
Private Bytes is memory that is allocated by the process and is a subset of
the virtual memory allocated counter. When it is allocated/freed is
entirely dependent on how the application is denied. If you are using .Net,
then GC will be a factor. If you create a lot of long-lived data structures
(i.e. cache) then you will see it go up at first, then level off. On ASP,
for example:
<%
myStr = "This is a test" <--Memory allocated
Response.Write myStr <--Memory in the Response buffer is allocated
Response.Flush <--Memory in the response buffer is freed
%>
Page is done, memory used for myStr is freed.
Pat
"lan" <lan@online.microsoft.com> wrote in message
news:OKfNktG5EHA.3124@TK2MSFTNGP11.phx.gbl...
> Running win2003 server. The private bytes of w3wp slightly increased, but
> virtual bytes of w3wp is stable. How does IIS handle memory allocation?
> Once a request is finished, will IIS mark those allocated memory as
> free(not referenced)? and waiting GC to collect?
>
- Next message: Pat [MSFT]: "Re: 2003 Server, quad proc, IIS box - CPU @100%"
- Previous message: Pat [MSFT]: "Re: IIS State Log Analysis"
- In reply to: lan: "IIS memory issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
