I am running into the issue where our exchange server is eating all of the free RAM and I understand that by design it is supposed to do this and then release some ram to run other programs, etc. However, I am looking to try and put a cap on it if possible.
I have tried to set the msExchESEParamaCacheSizeMax in ADSI under the CN=Information Store. The value that I put in was how many 32kb pages I want Exchange to use 393216 (which is 12GB). I then restarted the information store service and check the ram usage this morning and its back to using 21GB.
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Can you help the group out and explain why you want to do this? Is there something else on the box that needs the memory? The thing is that Exchange will hand memory back if properly requested so you should not, under any real circumstances, need to mess about with settings.
The reason I am looking to do this is because I am getting very high pages/sec between 100-500 and since the client did not want to purchase separate servers for the DC, SQL, Exchange and other roles; all the roles are installed on one server. I understand that Exchange is built to work that way with the RAM but I need to limit the amount it can use.
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Oh right, I see. Sorry, I think you should have been told to buy SBS not all three products. You can't work that way with all those things. It's supported but not recommended. If you can't virtualise them I would raise merry-hell with whoever sold you that mix and get SBS instead.
If you have found that you did actually get SBS then don't worry, your server is optimised to handle the load.
While what Mark says is true about the utilization and release of memory in Exchange -- limiting the RAM isn't such a taboo move, especially in your circumstance.
By setting the number too low, you could cause drastic slowness and login problems..Exchange does a mighty fine job of using memory and freeing it upon request, but there are situations in which limiting the cache will provide an overall better experience for all services provided by the server.
Try using 524288 as your cache limit..that will do a 16GB limit (I dont think you can do a 12 GB limit) and then restart the information store. I know this setting worked prior to SP1 on a couple of my servers that needed a limitation set..I don't think I've seen this setting work successfully since SP1, but I could be wrong.
If that works, I'd highly suggest going to 20 or 22 GB cache limits.
I've adjusted the cache limit and restarted the Info Store. I will let you know if it works. It was a SP1 installation to start with (most difficult installation I have ever had with Exchange!!) Im surprised that they haven't fixed the installation to include all the hotfixes!
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Really, nathan, you should look at following the Hyper-V or multi box route. You are never going to be happy trying to tweak this and that, here and there. You are always going to be looking over your shoulder and changing settings. It's just not worth losing your sanity over.
Used this link and it worked fine, try to you the number placed on the link and see if it limits it to that. 131072 for 4GB ( weird calculations... didnt have time too understand)
That's what the user has already done..it appears that setting doesn't have any barring on Exch2010 SP1.
Switching to hyper V wont make a difference..you cannot limit the service memory usage on the server with hyper-v. The user isn't wanting to limit the RAM on the server, rather, limit the RAM used by the information store.
Unfortunately I dont think there is anything you can do at this point other than move the non-Exchange services to another host / server.
I dont think MS would mess up something like that on SP1, if so there would be ppl complaining about it.
I posted the link so the person asking to try the amount mention on it. 4GBs and se if it works, and as I read on that link and understood is the sizes has to be on the dot, how you calculate the number? I dont know and dont care, since I only need to limited to 4GB.
As for working with DC and Exchange on the same server.... it works fine! no slowdowns in any way, just as long as Exchange Store size is limited and you have at least 2Gb free.
So nathan2343 just try 131072 for 4GB and see what happens. I would sugest restarting the whole server because, when I tried to restart the store process, it didnt work, only after restarting the server.
Hope it helps.
And it doesn't hurt to try again. :P sometimes we do things wrong and not notice it. if it doesn't work then fine i'll except that there is something else wrong.
_____________________________
A team of highly trained monkeys has been dispatched to deal with this situation.
Earlier we already suggested modifying the active directory object. I've noticed it on my SP1 servers also..the value doesn't make a difference anymore. I went ahead and setup a new Exchange 2010 RTM server in my network and I was able to limit the information store cache..I then upgraded to SP1 and while the value was still present in active directory..it no longer limited the cache size of the IS.
The calculation is simple...(((4 x 1024) x 1024) / 32) = 131072
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2010] >> General >> Limiting RAM usage 
Limiting RAM usage - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
