INTRODUCTION
This is the third CXP flash about Windows 2003 kernel memory issues and Exchange 2003.
The first flash provided technical background about the demands Exch...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Guys, love the site, great article. Mabye you can clean up a little confusion on my end. I thouht that under W2K if you enabled the Non-Paged pool (NP Pool) was limited to 256MB and with the /3GB switch the NP Pool was reduced by 50% to 128MB. When we were running EX2K on W2K we would start to see problems when the NP Pool reached about 96MB.
Now in this article you mention that by default in W2K3 that the NP Pool is 350MB and when using the /3GB switch it reduced to 250MB. Did MS increase the the amount of memory that the kernal allocates to the NP Pool in W2K3?
A related Q on PCI-E servers this blog has mentioned that we should also implement /PAE (to deal with the way PCI-E allocates RAM on servers with large amounts of RAM) how does this effect NP Pool consumption on W2K3 any clarification would be appreciated as it would help us (and your other readers) better monitor their systems.
Many Thanks,
M@
Now in this article you mention that by default in W2K3 that the NP Pool is 350MB and when using the /3GB switch it reduced to 250MB. Did MS increase the the amount of memory that the kernal allocates to the NP Pool in W2K3?
A related Q on PCI-E servers this blog has mentioned that we should also implement /PAE (to deal with the way PCI-E allocates RAM on servers with large amounts of RAM) how does this effect NP Pool consumption on W2K3 any clarification would be appreciated as it would help us (and your other readers) better monitor their systems.
Many Thanks,
M@