ZEN AND THE ART OF PERFORMANCE MONITORING 375 If I am looking for the process that is using up most of the CPU time, then I click the CPU column and sort based on the current percentage of CPU usage. On a reasonably idle server, the System Idle Process will be entertaining the CPU most of the time. If you have looked at your own server, you may be saying to yourself, Self, what in the world is store.exe , and does it have a memory leak? In Figure 9.2, store.exe is currently occupying 595MB of RAM and peaked at 875MB. The store.exe file will generally use all of the memory it can on an Exchange server; it is a feature, not a bug. The store (and the ESE database engine) allocates as much memory for caching as possible up to a certain point. Even after running Exchange 2003 for more than two-and-a-half years, I have never seen the store.exe occupy more than 2GB of RAM. For optimum memory usage, though, make sure the BOOT.INI file is using the /3GB / USERVA=3030 switches for Windows 2003 or /3GB for Windows 2000 Advanced Server. Other processes in the Image Name list include inetinfo.exe ; this is Internet Information Services (IIS) and all of its components including web services, POP3, IMAP4, FTP, SMTP, or other services you have enabled. On a heavily used OWA or SMTP server, you can expect inetinfo.exe to easily occupy a few hundred megabytes of RAM. The mad.exe file (the Mailer Administrative Daemon) is better known as the System Attendant. The System Attendant on a busy server will often climb up to more than 100MB of RAM. Much of the rest of the processes you see in Figure 9.2 are actually processed launched by Symantec Mail Security for Microsoft Exchange and are not native Windows or Exchange 2003 processes. The final property page in the Task Manager that may prove useful when you need a quick look at current performance is Networking. The Networking property page shows the average network usage over the last few minutes. Before making any rash judgments as to the state of your server s network connection, look closely at the scale to the left. For example, the Networking property page in Figure 9.3 looks reasonably busy, but look at the scale it only peaked a few times to more than 12.5 percent usage. This particular figure shows a production server with approximately 475 active users plus my Remote Desktop Connection. Figure 9.3 Analyzing average networking usage using Task Manager

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Low Cost Web Hosting services

Bookmark the permalink.

Comments are closed.