Sharepoint 2007/2010 – Website – Performance Monitor

Sharepoint 2007/2010 – Website – Performance Monitor






Requests Current: The current number of requests, including those that are queued, currently executing, or waiting to be written to the client.  Under the ASP.NET process model, when this counter exceeds the requestQueueLimit defined in the processModel configuration section, ASP.NET will begin rejecting requests.



Requests Time Out: The number of requests that timed out.

 Requests Total: The total number of requests since the application was started.

 Requests/Sec: The number of requests executed per second.

Session Total: Total number of sessions since the application was started.



PhysicalDisk : % Disk Time. Much like % Processor time, this counter is a general mark of how busy the disk is. You will see many similarities between the disk and processor since they are both transaction-based services. This counter indicates a disk problem, but must be observed in conjunction with the Current Disk Queue Length counter to be truly informative. Recall also that the disk could be a bottleneck prior to the % Disk Time reaching 100%

Logs the amount of time for which disk is active during the last monitoring period. Values higher than 80% indicate that there may be a problem with the hard drive controller or insufficient memory.

PhysicalDisk : Current Disk Queue Length. This counter provides a primary measure of disk congestion. Just as the processor queue was an indication of waiting threads, the disk queue is an indication of the number of transactions that are waiting to be processed. Recall that the queue is an important measure for services that operate on a transaction basis. Just like the line at the supermarket, the queue will be representative of not only the number of transactions, but also the length and frequency of each transaction.

Logs the number of the items waiting to be written to or read from the disk. Values higher than 2 indicate a problem with the disk subsystem. RAID 5 or RAID 10 should be implemented to improve performance.



Memory : Available Memory. This counter indicates the amount of memory that is left after nonpaged pool allocations, paged pool allocations, process’ working sets, and the file system cache have all taken their piece. In general, NT attempts to keep this value around 4 MB. Should it drop below this for a sustained period, on the order of minutes at a time, there may be a memory shortage. Of course, you must always keep an eye out for those times when you are simply attempting to perform memory intensive tasks or large file transfers.

Monitors the amount of memory available to the system. Values below 10% of total physical memory indicate the need for more RAM.

Memory : Page Faults/sec. This counter gives a general idea of how many times information being requested is not where the application (and VMM) expects it to be. The information must either be retrieved from another location in memory or from the pagefile. Recall that while a sustained value may indicate trouble here, you should be more concerned with hard page faults that represent actual reads or writes to the disk. Remember that the disk access is much slower than RAM.

Records the number of times that data was not found in memory.

Memory : Pages/sec. This value is often confused with Page Faults/sec. The Pages/sec counter is a combination of Pages Input/sec and Pages Output/sec counters. Recall that Page Faults/sec is a combination of hard page faults and soft page faults. This counter, however, is a general indicator of how often the system is using the hard drive to store or retrieve memory associated data.

Monitors the data written to or read from memory. Values higher than 200 indicates the need to increase RAM.

Process : Pool Paged Bytes. This is the amount of memory that the process is using in the pageable memory region. This information can be paged out from physical RAM to the pagefile on the hard drive.

Records the amount of data that cannot be paged on the disk.



Process : % Processor Time. This counter is a natural choice that will give use the amount of time that this particular process spends using the processor resource. There are also % Privilege Time and % User Time counters for this object that will help to identify what the program is spending most of its time doing.

Records the current CPU utilization. This log helps determine the need for additional processor capacity.

Processor : Interrupts /sec. The numbers of interrupts the processor was asked to respond to. Interrupts are generated from hardware components like hard disk controller adapters and network interface cards. A sustained value over 1000 is usually an indication of a problem. Problems would include a poorly configured drivers, errors in drivers, excessive utilization of a device (like a NIC on an IIS server), or hardware failure. Compare this value with the System : Systems Calls/sec. If the Interrupts/sec is much larger over a sustained period, you probably have a hardware issue.

Records the number of times processing is stopped to handle a hardware request for disk or memory I/O. Values higher than 1000 may indicate a hardware issue.



System : Processor Queue Length. Oddly enough, this processor counter shows up under the System object, but not without good reason. There is only 1 queue for tasks that need to go to the processor, even if there is more than one CPU. Thus, counter provides a measure of the instantaneous size of the queue for all processors at the moment that the measurement was taken. The resulting value is a measure of how many threads are in the Ready state waiting to be processed. When dealing with queues, if the value exceeds 2 for a sustained period, you are definitely having a problem with the resource in question.

Logs the number of items waiting to be processed by the CPU. Values higher than 2 indicates the need to add more or faster processors


Source: Microsoft


2 thoughts on “Sharepoint 2007/2010 – Website – Performance Monitor

  1. Thanks for your article on this site. From my own personal experience, many times softening right up a photograph might provide the photographer with
    a little bit of an inspired flare. Often however, that soft blur isn’t what precisely you had as the primary goal and can often times spoil an otherwise good image, especially if you anticipate enlarging this.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s