In troubleshooting problems with our IIS servers, a number of people (from
MS, this group, etc.) have indicated that we most likely have a problem with
heap fragmentation.  We just ran across an MS KB article Q315407 for
Exchange that talks about creating a registry called
"HeapDecommitFreeBlockThreshold" entry to reduce heap fragmentation.
Although I have only seen this in articles related to Exchange, I am
wondering if it is safe to apply to servers not running Exchange, such as
our IIS servers.

Any info on this would be appreciated,

Thanks,

Pete COnlan

[ Post a follow-up to this message ]

It is unlikely to help.  The vast majority of heap fragmentation issues are
actually caused by very small memory leaks.  The reason is b/c memory
allocations must be contiguous.  If there is even an 8 byte allocation in
the middle of a 1 MB memory block, then the most you could allocate would be
512k (assuming the leak had occurred in the dead center of the memory
block).

Pat

"PeterConlan" <anonymous@discussions.microsoft.com> wrote in message
news:u%23iBBYipEHA.4076@TK2MSFTNGP12.phx.gbl...
> In troubleshooting problems with our IIS servers, a number of people (from
> MS, this group, etc.) have indicated that we most likely have a problem
> with
> heap fragmentation.  We just ran across an MS KB article Q315407 for
> Exchange that talks about creating a registry called
> "HeapDecommitFreeBlockThreshold" entry to reduce heap fragmentation.
> Although I have only seen this in articles related to Exchange, I am
> wondering if it is safe to apply to servers not running Exchange, such as
> our IIS servers.
>
> Any info on this would be appreciated,
>
> Thanks,
>
> Pete COnlan
>
>

[ Post a follow-up to this message ]