David
Wed Feb 15 05:34:15 CST 2006
http://blogs.msdn.com/david.wang/archive/2006/02/14/More_on_Virtual_Memory_Memory_Fragmentation_and_Leaks_and_WOW64.aspx
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"sam" <sam_fanny@hotmail.com> wrote in message
news:uVzF9u$JGHA.720@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> Thanks for the info.
> Sorry i was not clear. I am recycling the memory based upon the virtual
> memory size. I presumed that by virtual memory it means memory stored on
> disk in the page file. Is this not the case?
>
> There is still physical ram free on the machine when i see the out of
> memory problems leading me to suspect either a memory leak or memory
> fragmentation. I see the virtual bytes counter rise quickly to 1500mb (2-3
> times a day) whereas the physical Ram used by the w3wp process is only a
> few hundred MB with plenty of RAM left to spare. I'm not sure why the
> virtual memory grows so high when there is enough Physical RAM. I have
> tried using DebugDiag but the report generated is too high a level for me
> to understand without more documentation.
> An example from the DebugDiag report on the w3wp process when it had a
> high virtual memory usage:
> Virtual Memory Summary
> Size of largest free VM block 75.21 MBytes
> Free memory fragmentation 88.13%
> Free Memory 633.53 MBytes (30.93% of Total Memory)
> Reserved Memory 1.03 GBytes (51.29% of Total Memory)
> Committed Memory 364.06 MBytes (17.78% of Total Memory)
> Total Memory 2.00 GBytes
> Largest free block at 0x00000000`685ba000
>
>
> This is the heap I identified as using the most memory
>
> Heap Name msvcrt!_crtheap
> Heap Description This heap is used by msvcrt
> Reserved memory 868.25 MBytes
> Committed memory 89.16 MBytes (10.27% of reserved)
> Uncommitted memory 779.10 MBytes (89.73% of reserved)
> Number of heap segments 12 segments
> Number of uncommitted ranges 8207 range(s)
> Size of largest uncommitted range 32.20 MBytes
> Calculated heap fragmentation 95.87%
>
>
> Top Allocation - Allocation Size - 1048 29.42 MBytes 29435 allocation(s)
>
> There are 12 heap segments and nearly all have extremely high
> fragmentation and they have allocated a lot of reserved memory. The
> commited size in each segment is very low so i'm unsure why that is the
> case and where i go from here to debug the application further. This has
> been driving me nuts for months now and there isn't anyone i know to ask
> other than you experts who write this stuff...
>
> Going back to your article you say that i should run the ASP on iis in a
> 64 bit process and that it will automatically create a seperate dll host
> for all the 32 bit com objects. Do i need to set the flag
> Enable32BitAppOnWin64 for this to work? How do i register the 32 bit
> components. Is it a case of simply using regsvr32?
>
> Thanks for your time.
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:em1LpS%23JGHA.3352@TK2MSFTNGP12.phx.gbl...
>>
http://blogs.msdn.com/david.wang/archive/2006/02/01/ASP_Application_Large_Memory_Needs_and_64bit_IIS6.aspx
>>
>> Not certain how memory recycling have anything to do with paging file
>> size because you want as much RAM as possible to avoid the disk, and
>> memory recycling limits the amount of RAM used... so why are you worrying
>> about paging file size?
>>
>> --
>> //David
>> IIS
>>
http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "sam" <sam_fanny@hotmail.com> wrote in message
>> news:OuGsBJ5JGHA.2900@TK2MSFTNGP14.phx.gbl...
>>> Hi,
>>>
>>> I am wanting to run an ASP application on Windows 2003 64 bit edition.
>>> Because some of the COM components are compiled on 32 bit machines i
>>> understand that i have to run IIS in WOW64 compatibilty mode.
>>> Does this mean i will have the same memory limitations per process of
>>> w3wp.exe (2GB) ? Do i get any benefit memory wise running IIS in this
>>> mode on windows 2003 64 bit edition? My main issue is that my
>>> Application Pool recycles too fast. I have it recycle at 1500mb because
>>> at a setting higher than this i get memory problems. Could i increase
>>> this to something like 3000mb on Windows 2003 64 bit and if so what
>>> would you reccommend the paging file size be on the disk and physical
>>> ram?
>>>
>>> Thanks.
>>>
>>> Sam.
>>>
>>
>>
>
>