Ex2k7 - Pool Paged Memory - Recommended Alert Threshold?

R. @discussions.microsoft.com Nick R.

unread,

Aug 26, 2009, 1:45:01 PM8/26/09

to

Hello,

One of our alerting systems has a pre-configured rule that would send alerts
when our Exchange 2007 servers goes about 335544320 bytes of Pool Paged
memory. In the last month or so we have regularly exceeded this threshold.

My question is - On Exchange 2007 SP1 running on Windows 2008 SP1 (64-bit of
course) with 12GB of RAM and 12GB of swap space does crossing this pool paged
memory threshold indicate any issues, or is this just a pre-canned alert that
needs to be modified? On the 32-bit platforms this memory was more restricted
but from what I've read so far on 64-bit platforms this is no longer the
case.

We haven't heard any reports of users having issues connecting up to
Exchange and we are on the latest Rollup release.

scottb

unread,

Dec 21, 2009, 12:13:39 AM12/21/09

to

the following article may help:

http://technet.microsoft.com/en-us/library/cc671175(EXCHG.80).aspx

we have the same monitoring solution I think and have this alert on one server. The above article indicates that pool and nonpool memory does not need to be monitored, but I would think you need to set it to something??

Nick R. wrote:

Ex2k7 - Pool Paged Memory - Recommended Alert Threshold?
26-Aug-09

Hello,

One of our alerting systems has a pre-configured rule that would send alerts
when our Exchange 2007 servers goes about 335544320 bytes of Pool Paged
memory. In the last month or so we have regularly exceeded this threshold.

My question is - On Exchange 2007 SP1 running on Windows 2008 SP1 (64-bit of
course) with 12GB of RAM and 12GB of swap space does crossing this pool paged
memory threshold indicate any issues, or is this just a pre-canned alert that
needs to be modified? On the 32-bit platforms this memory was more restricted

but from what I have read so far on 64-bit platforms this is no longer the
case.

We have not heard any reports of users having issues connecting up to

Exchange and we are on the latest Rollup release.

Previous Posts In This Thread:

On Wednesday, August 26, 2009 1:45 PM
Nick R. wrote:

Ex2k7 - Pool Paged Memory - Recommended Alert Threshold?
Hello,

One of our alerting systems has a pre-configured rule that would send alerts
when our Exchange 2007 servers goes about 335544320 bytes of Pool Paged
memory. In the last month or so we have regularly exceeded this threshold.

My question is - On Exchange 2007 SP1 running on Windows 2008 SP1 (64-bit of
course) with 12GB of RAM and 12GB of swap space does crossing this pool paged
memory threshold indicate any issues, or is this just a pre-canned alert that
needs to be modified? On the 32-bit platforms this memory was more restricted

but from what I have read so far on 64-bit platforms this is no longer the
case.

We have not heard any reports of users having issues connecting up to

Exchange and we are on the latest Rollup release.

Submitted via EggHeadCafe - Software Developer Portal of Choice
Client-Side Real-Time Stock Quote ScreenScraping
http://www.eggheadcafe.com/tutorials/aspnet/50984b0e-f52d-4b01-8889-dce6a1077593/clientside-realtime-sto.aspx

John Fullbright

unread,

Dec 29, 2009, 2:33:01 AM12/29/09

to

You should follow Mike Lagase's blog.
http://blogs.technet.com/mikelag/archive/2009/08/20/exchange-2007-memory-usage-and-helpful-troubleshooting-tips.aspx

I remember the issue with antivirus causing the system cache to increase and
trigger a working set trim quite well.

"Scott B" wrote:

> .
>