Memory Peformance in Exchange Servers

Memory was classified as

  1. Kernal Memory
  2. User Mode Memory

 Windows 32-bit Operating Systems implement a virtual memory system based on a flat 32-bit address space.  32-bits of address space translates into 4GB of virtual memory.  A process can access up to 4GB of memory address space by using the /3GB switch changes this behavior

 Whenever the Exchange server boots up the memory manager creates two dynamically sized memory pools knows as 

  1. Paged Pool Memory
  2. Non – Paged Pool Memory

 Paged Pool Memory – Memory that can be paged out

Non – Paged Pool Memory – Memory which cannot be paged out. Example Drives uses the Nonpaged Pool because they can be accessed at IRQ 

Memory Table –       Windows 2003

System RAM NonPaged Max Paged Max
512 MB 125 MB 184 MB
1024 MB 202 MB 168 MB
1536 MB 254 MB 352 MB
2048 MB 252 MB 352 MB

 In order to determine the memory utilization use the below tool 

  1. Process Explore.exe –  Configure the symbol by mentioning the below path (srv*c:\symbols* 
  2. Poolmon and Perfmin 

The Pool Resources get depleted and the below cause will occur

  • users can no longer log on to the machine
  • the machine becomes sluggish
  • console access is sluggish
  • users cannot connect to file shares or other shared resources
  • system hangs including the console itself being unresponsive

About Raji Subramanian

Nothing great to say about me...Just want to share my knowledge for others that will be useful at any moment of time when they stuck in critical issue....
This entry was posted in Performanace. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s