I have Exchange 2007 running on Server 2003 R2, 64 Bit. The machine has Dual processors, and 18GB of memory, and a RAID-5 array. The datastore is about 20GB in size. Continuous local replication is enabled to the local disk. I support about 100 mailboxes, but only about 8 concurent users. The users have access to multiple mailboxes, many of which are shared, including about 5,000 shared contacts. The 8 users are using Outlook 2010, running in non-cached mode. I also have a half-dozen applications sending internal email, and use Symantec Endpoint protection to scan for viruses and as my secondary spam block. (My primary spam filter is off-site). An additional 20 users login about once per day to pick up a few emails.
The Server also serves as my backup DC, and as file storage. The files are relatively small, so accessing them is not a big demand on the system.
The Exchange process store.exe uses (at times) tremendous amounts of memory (12GB to 13GB). It will then, for no apparent reason, go down to 4GB and stay there for a while. Then up, then down.
My users complain that there are sometimes delays in accessing their files (including application not responding delays). These are 40K read-only files, so it can't be a big demand on the system. (The files are accessed through DFS, but all copies are on the local subnet and this sever is the primary source). I want to make sure that Exchange is no using up so much memory that it is pushing back file access.
Is Exchange using too much memory? Any suggestions on how to make sure my users will not have delays in accessing their files?