Baseline Performance Model in Microsoft Office

Generation UPC-A Supplement 2 in Microsoft Office Baseline Performance Model

The task of monitoring should begin long before your users begin using your new MOSS environment By establishing a baseline performance model, you can establish what your MOSS environment looks like under no load, average load, and peak load This knowledge is incredibly useful for preventing performance bottlenecks and allowing you to proactively address them before they impact your users Knowing what a healthy performance baseline looks like will also help with troubleshooting existing performance issues

13:

Depending on your server configuration, not all of the performance objects and counters listed in Table 13-1 may be available The performance counters listed in Table 13-1 represent only one recommended model As you work with your particular MOSS environment, you may choose to monitor additional performance counters, depending on your server configuration and the quality of service (QoS) requirements of your users

Include in Baseline Yes Yes Yes Optional Yes Optional Yes Yes Yes Yes Yes Optional Optional Optional

Performance Object Memory Memory Memory System Processor Network Process Process Web Service ASPNET Web Service Web Service Web Service NET Common Language Runtime (CLR) Data NET CLR Data SQL Server

Counter Available Mbytes % Committed Bytes in Use Pages/second Processor Queue Length % Processor Time Network Queue Length % Processor Time Private Bytes Connection Attempts/Sec Worker Process Restarts Current Connections Bytes Sent/Sec Bytes Received/Sec SQL Client: Current # Pooled and Non-Pooled Connections SQL Client: Failed Pooled Connections % Processor Time

All Servers Memory Memory Memory Processor Processor Network Web Front- Process End Server Process Application load Application load Application load Network Network Application load

It is very important to establish a baseline performance model of a newly installed MOSS environment before users begin to put a load on the system To create a baseline performance model, perform the following steps: 1 Start the Performance Console by clicking the Start button in the taskbar, choosing Administrative Tasks, and finally Performance 2 Expand the Performance Logs and Alerts node in the folder pane and then select Counter Logs 3 Right-click anywhere in the detail pane (right side of the Performance window) and select New Log Settings 4 Name the log SharePoint Baseline and click OK 5 Use the Add Counters button, as shown in Figure 13-10, to add the counters indicated in Table 13-1 as recommended for inclusion as a baseline counter 6 If your SharePoint environment consists of more than one server, repeat this process for each server in your environment, paying attention to the server roles (as illustrated in Figure 13-4)

13:

As a SharePoint administrator, you definitely need to monitor how MOSS is consuming server resources On any system, the four major server resources are CPU, memory, disk space, and network bandwidth These four resources combine to indicate the overall health of your MOSS environment When analyzed together, they provide you with a fairly good idea of how responsive MOSS is for your users Table 13-2 lists the operating limits recommended for an MOSS environment As indicated, CPU utilization should not exceed 80 percent regularly At least 50MB of primary memory should be available for the system, available hard disk space should not drop below 10 percent, and the bandwidth for MOSS clients should remain at or above 256 KBps Should the MOSS system, or the operating system for that matter, on any of the network s servers begin operating below normal standards, your first investigation should be to determine if one of the limits listed in Table 13-2 has been exceeded and begin using the event logs to determine the cause Of course, the cause could also be that the available resources needed for the system may need to be enhanced or upgraded

On the Operations page of the MOSS Central Administration site, the section entitled Logging and Reporting (see Figure 13-11) provides you with three general areas in which you can apply logging and reporting functions The information collected and reported in each of these areas is designed to provide you with the capability to diagnose, analyze, and monitor the performance of your MOSS environment The three areas included in the Logging and Reporting section are: Diagnostic logging Usage analysis processing Information management policy usage reports