Performance Counters for the MSRS 2008 Web Service Performance Object
This topic describes performance counters for the MSRS 2008 Web Service performance object that is part of a SQL Server 2008 Reporting Services deployment.
Note
This performance object is used to monitor events on the local report server. If you are running a report server in a scale-out deployment, the counts apply to the current server and not the scale-out deployment as a whole.
Performance objects are available in the Windows Performance Console (in Windows 2000 Server and Windows Server 2003) and in the Windows Reliability and Performance Console (in Windows Vista and Windows Server 2008). For more information, see your Microsoft Windows documentation.
MSRS 2008 Web Service Performance Counters
The MSRS 2008 Web Service performance object is used to monitor report server performance. This performance object includes a collection of counters used to track report server processing typically initiated through interactive report viewing operations. When you set up this counter, you can apply the counter to all instances of Reporting Services or you can select specific instances. These counters are reset whenever ASP.NET stops the Report Server Web service.
The following table lists the counters that are included with the MSRS 2008 Web Service performance object.
Counter |
Description |
|---|---|
Active Sessions |
Number of active sessions. This counter provides a cumulative count of all browser sessions generated from report subscriptions, whether they are still active or not. The counter is decremented as session records are removed. By default, sessions are removed after ten minutes of no activity. |
Cache Hits/Sec |
Number of requests per second for cached reports. These are requests for re-rendered reports, not requests for reports processed directly from the cache. (See Total Cache Hits later in this topic.) |
Cache Misses/Sec |
Number of requests per second that failed to return a report from cache. Use this counter to find out whether the resources used for caching (disk or memory) are sufficient. |
First Session Requests/Sec |
Number of new user sessions that are started from the report server cache each second. |
Memory Cache Hits/Sec |
Number of times per second that reports are retrieved from the in-memory cache. In-memory cache is a part of the cache that stores reports in CPU memory. When in-memory cache is used, the report server does not query SQL Server for cached content. |
Memory Cache Misses/Sec |
Number of times per second that reports could not be retrieved from the in-memory cache. |
Next Session Requests/Sec |
Number of requests per second for reports that are open in an existing session (such as reports that are rendered from a session snapshot). |
Report Requests |
Number of reports that are currently active and being handled by the report server. |
Reports Executed/Sec |
Number of successful report executions per second. This counter provides statistics about report volume. Use this counter with Request/Sec to compare report execution to report requests that can be returned from cache. |
Requests/Sec |
Number of requests per second made to the report server. This counter tracks all types of requests that are handled by the report server. |
Total Cache Hits |
Total number of requests for reports from the cache after the service started. This counter is reset whenever ASP.NET stops the Report Server Web service. |
Total Cache Misses |
Total number of times that a report could not be returned from the cache after the service started. This counter is reset whenever ASP.NET stops the Report Server Web service. Use this counter to determine whether disk space and memory are sufficient. |
Total Memory Cache Hits |
Total number of cached reports returned from the in-memory cache after the service started. This counter is reset whenever ASP.NET stops the Report Server Web service. In-memory cache is a part of the cache that stores reports in CPU memory. When in-memory cache is used, the report server does not query SQL Server for cached content. |
Total Memory Cache Misses |
Total number of cache misses against the in-memory cache after the service started. This counter is reset whenever ASP.NET stops the Report Server Web service. |
Total Processing Failures |
Total number of report processing failures that have occurred after the service started. This counter is reset whenever ASP.NET stops the Report Server Web service. Processing failures can originate from the report processor or any extension. |
Total Rejected Threads |
Total number of data processing threads rejected for asynchronous processing, and subsequently handled as synchronous processes in the same thread. Each data source is processed on one thread. If the volume of threads exceeds capacity, threads are rejected for asynchronous processing, and are then processed in a serial manner. |
Total Reports Executed |
Total number of reports that ran successfully after the service started. This counter is reset whenever ASP.NET stops the Report Server Web service. |
Total Requests |
Total number of all requests made to the report server after the service started. This counter is reset whenever ASP.NET stops the Report Server Web service. |