|
Troubleshooting performance problems is a key reason for monitoring IIS. Another common reason for wanting to monitor IIS is to use the results to improve server performance. Improving server performance can reduce the need for costly additional servers or additional hardware components, such as central processing units (CPUs) and memory. This allows you to squeeze additional processing power out of the server and budget for when you really need to purchase new servers and components.
To achieve optimal performance, you need to identify performance bottlenecks, maximize throughput, and minimize the time it takes for Web applications to process user requests. You achieve this by doing the following:
| • | Monitoring memory and CPU usage and taking appropriate steps to reduce the load on the server, as necessary. Other processes running on the server may be using memory and CPU resources needed by IIS. Resolve this issue by stopping nonessential services and moving support applications to a different server. |
| • | Resolving hardware issues that may be causing problems. If slow disk drives are delaying file reads, work on improving disk input/output (I/O). If the network cards are running at full capacity, install additional network cards for performing activities, such as backups. |
| • | Optimizing Web pages and applications running on IIS. You should test Web pages and IIS applications to ensure the source code performs as expected. Eliminate unnecessary procedures and optimize inefficient processes. |
Unfortunately, there are often tradeoffs to be made when it comes to resource usage. For example, as the number of users accessing IIS grows, you may not be able to reduce the network traffic load, but you may be able to improve server performance by optimizing Web pages and IIS applications.
BMC Performance Manager Express for SharePoint enables administrators to monitor various IIS metrics:
Global Performance
.NET CLR Memory
The performance console .NET CLR Memory category includes counters that provide information about the garbage collector. BMC Performance Manager Express for SharePoint provides three performance counter:
|
|
|
# Bytes In All Heaps
|
Displays the sum of the Gen 0 Heap Size, Gen 1 Heap Size, Gen 2 Heap Size, and the Large Object Heap Size counters. This counter indicates the current memory allocated in bytes on the garbage collection heaps.
|
% Time In GC
|
Displays the percentage of elapsed time that was spent performing a garbage collection since the last garbage collection cycle. This counter usually indicates the work done by the garbage collector to collect and compact memory on behalf of the application. This counter is updated only at the end of every garbage collection. This counter is not an average; its value reflects the last observed value.
|
Large Object Heap Size
|
Displays the current size, in bytes, of the Large Object Heap. Objects greater than 20 KB are treated as large objects by the garbage collector and are directly allocated in a special heap; they are not promoted through the generations. This counter is updated at the end of a garbage collection, not at each allocation.
|
Asp .Net
BMC Performance Manager Express for SharePoint provides the status of the Worker Process Restarts performance counter that indicates the number of times a worker process has been restarted on the server computer.
Process
BMC Performance Manager Express for SharePoint monitors the SharePoint processes and reports the following metrics for all of the w3wp.exe processes:
|
|
|
% Processor time
|
The average percentage of processor used for each processor
|
Handle Count
|
Total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.
|
Private Bytes
|
Size in bytes that this process has allocated that cannot be shared with other processes.
|
Working Set
|
Current size of the memory area that the process is utilizing for code, threads, and data. The size of the working set grows and shrinks as the VMM permits.
|
Web Service (_Total)
BMC Performance Manager Express for SharePoint monitors main Web service performance object counters (installed with Internet Information Services).
|
|
|
Bytes received/sec
|
Rate in incidents per second at which data bytes were received by the web service.
|
Bytes sent/sec
|
Rate in incidents per second at which data bytes were sent by the web service.
|
Current Connections
|
Current number of connections established with the Web service
|
|
