This one's useful, perhaps: "Understanding Exchange 2007 Memory Usage and its use of the Paging File"
http://msexchangeteam.com/archive/2008/08/06/449484.aspx Cheers, Phil -- Phil Randal Networks Engineer Herefordshire Council Hereford, UK -----Original Message----- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: 07 August 2008 13:50 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007, memory usage, and hunt the thimble In another email in this thread, you also mentioned that it was the DC/GC. I would start with Perfmon, using the counters I named below (and I'd also be looking at disk queuing at the same time). Then exbpa. You should be able to quickly determine the problem. Fixing it may be a tad more challenging, but identifying it is cake. Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2008 3:44 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007, memory usage, and hunt the thimble What leads me to ask? Well partly a general curiosity. Having a server who's memory is constantly in use fires off loads of alerts (here at least) and these alerts go to more people than just me, so questions will get asked, especially as we just upgraded the ram. Secondly, the server runs like a one legged dog with a bad foot. Everything exchange related from the exchange 2007 interface which redraws in small squares (god how I miss the ADUC integration, where did that go, hey?) to users complaining of 3+ seconds to open an email (frankly I don't think thats awful but hey-ho) and regularly up to 10 seconds. Flicking between email folders is the same. If it were a 2003 box I would say it needs more ram or look at replacing the sata disks, as it feels like a sata disk issue perhaps. However in this case we are running SAS disks, with lots of space etc. The server is only exchange, all the file duties are handled by an SVN box next door and sharepoint is on a separate server too. Olly -----Original Message----- From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: 06 August 2008 16:05 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007, memory usage, and hunt the thimble I consider these the key performance counters used for looking at memory utilization on an Exchange Server: Memory\Pages/Sec Memory\% Committed Bytes In Use Memory\Available Mbytes Note that memory-in-use has little correlation with MEMORY PRESSURE, which is much more important on an Exchange Server. I use the same memory chart that Kevin recommends for initial memory sizing on my servers. So...what led you to add more memory? Why do you think you may need even more? Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Bingham, Kevin [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2008 10:34 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007, memory usage, and hunt the thimble You start with the easy step of following one of the memory planning guides, like the simple one in TechNet: http://technet.microsoft.com/en-us/library/bb738124(EXCHG.80).aspx which uses things like server roles, number of mailboxes and number of storage groups, and whether you are doing any clustering or replication, to suggest your minimum recommended RAM requirements -- none of which are in your listed specs. After that, there are more complex things you can do for monitoring like page hits, disk I/O, and RPC latency... but if you hit the recommended targets from TechNet or many other sources, you're probably good. -----Original Message----- From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2008 7:21 AM To: MS-Exchange Admin Issues Subject: Exchange 2007, memory usage, and hunt the thimble Hi chaps, If the store.exe process of Exchange 2007 is designed to consume as much memory as it can in order to bring the much vaunted (though I would say much missing) speed improvements, then how do you know when your server needs a memory upgrade? What I mean is that, if the memory is always around 95% in use, what indications are there that your exchange box may be running out of ram? We have an exchange 2007 machine running Win 2003 64bit with 8GB of ram in it. It used to have 4GB in it and, not knowing if it need more ram, we plumbed for adding another 4gb. Of course, it instantly used it all. For all I know, it could be needing 28GB and be slowly dying a ram-restricted death. So is there anything in place in Exch2007 now that will indicate when we do, correctly, need to look at additional ram ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ __________ Information from ESET NOD32 Antivirus, version of virus signature database 3335 (20080807) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3335 (20080807) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
