"Transam388" <Transam***@discussions.microsoft.com> wrote in message
news:3D3E0582-0095-4001-824B-3CDC09110E70@microsoft.com...
>I am looking into one of the classic memory issues within an Exchange 2003
> A/P cluster.  The non paged pool memory is getting to about 92Mb and
> causing
> the virtual HTTP instance to shut down.  I have been using poolmon and
> task
> manager to watch memory use and to see if anything continues to keep
> taking
> memory.  Storport came up but that appears not to be growing at all.
>
> After several hours no process or driver seems to be constantly consuming
> more memory.  What I am wondering is if at some point a cache was set to
> high
> and is using way to much non paged pool memory.  Hence the question...What
> parameters in Exchange have a direct affect on memory and non paged pool
> memory, IE: ESE params in ADSIEdit?  The server does have the /3GB switch
> and
> userva=2900 at current with 4GB memory.
>
> Thanks!

"Dgoldman [MSFT]" wrote:

> I would get an ExBpa of the server. Also what OS and service pack are you
> running? If it is Windows 2003 SP2 you will need to turn off  TPC TCP
> Chimney Offload, Receive-side Scaling (RSS) and NetDMA
>
> http://msexchangeteam.com/archive/2007/07/18/446400.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Dgoldman
> http://blogs.msdn.com/dgoldman
> Download OABInteg
> (http://gotdotnet.com/Community/UserSamples/Download.aspx?SampleGuid=A2338E73-F521-4071-9B1D-AAF49C346ACD)
>
>
> "Transam388" <Transam***@discussions.microsoft.com> wrote in message
> news:3D3E0582-0095-4001-824B-3CDC09110E70@microsoft.com...
> >I am looking into one of the classic memory issues within an Exchange 2003
> > A/P cluster.  The non paged pool memory is getting to about 92Mb and
> > causing
> > the virtual HTTP instance to shut down.  I have been using poolmon and
> > task
> > manager to watch memory use and to see if anything continues to keep
> > taking
> > memory.  Storport came up but that appears not to be growing at all.
> >
> > After several hours no process or driver seems to be constantly consuming
> > more memory.  What I am wondering is if at some point a cache was set to
> > high
> > and is using way to much non paged pool memory.  Hence the question...What
> > parameters in Exchange have a direct affect on memory and non paged pool
> > memory, IE: ESE params in ADSIEdit?  The server does have the /3GB switch
> > and
> > userva=2900 at current with 4GB memory.
> >
> > Thanks!
>
>
>

"Transam388" <Transam***@discussions.microsoft.com> wrote in message
news:5D0D0BA8-8E1E-4BA6-AF14-BF747B7762B0@microsoft.com...
> Well interestingly enough you mention SP2 we just loaded that this month.
> The EXPBA says everything is fine but something is not right.  You
> mentioned
> the TPC TCP Chimney offload, and recieve-side scaling, as well as NetDMA.
> Are these services or more protocols?  I appreciate this as this is very
> insightful and gives some depth to the issue and not just a do this.
> Thanks!
>
> "Dgoldman [MSFT]" wrote:
>
>> I would get an ExBpa of the server. Also what OS and service pack are you
>> running? If it is Windows 2003 SP2 you will need to turn off  TPC TCP
>> Chimney Offload, Receive-side Scaling (RSS) and NetDMA
>>
>> http://msexchangeteam.com/archive/2007/07/18/446400.aspx
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> Dgoldman
>> http://blogs.msdn.com/dgoldman
>> Download OABInteg
>> (http://gotdotnet.com/Community/UserSamples/Download.aspx?SampleGuid=A2338E73-F521-4071-9B1D-AAF49C346ACD)
>>
>>
>> "Transam388" <Transam***@discussions.microsoft.com> wrote in message
>> news:3D3E0582-0095-4001-824B-3CDC09110E70@microsoft.com...
>> >I am looking into one of the classic memory issues within an Exchange
>> >2003
>> > A/P cluster.  The non paged pool memory is getting to about 92Mb and
>> > causing
>> > the virtual HTTP instance to shut down.  I have been using poolmon and
>> > task
>> > manager to watch memory use and to see if anything continues to keep
>> > taking
>> > memory.  Storport came up but that appears not to be growing at all.
>> >
>> > After several hours no process or driver seems to be constantly
>> > consuming
>> > more memory.  What I am wondering is if at some point a cache was set
>> > to
>> > high
>> > and is using way to much non paged pool memory.  Hence the
>> > question...What
>> > parameters in Exchange have a direct affect on memory and non paged
>> > pool
>> > memory, IE: ESE params in ADSIEdit?  The server does have the /3GB
>> > switch
>> > and
>> > userva=2900 at current with 4GB memory.
>> >
>> > Thanks!
>>
>>
>>