Export (0) Print
Expand All

Performance Counters for MSRS 2005 Windows Service

This topic describes performance counters for the MSRS 2005 Windows Service that is part of a SQL Server 2005 Reporting Services deployment. The performance object is available in the Windows server Performance console (Perfmon.msc). You can access the Performance console from Administrative Tools in Windows 2000 Server and Windows Server 2003. For more information, see your Windows documentation.

The MSRS 2005 Windows Service performance object includes a collection of counters used to track report processing that is initiated through scheduled operations. Scheduled operations can include subscription and delivery, report execution snapshots, and report history.

This performance object is used to monitor Report Server Windows service. 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.

Counter Description

Active Sessions

Number of active sessions stored in the report server database. This counter provides a cumulative count of all usable browser sessions generated from report subscriptions, whether they are still active or not.

Cache Flushes/Sec

Number of cache flushes per second.

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.

Delivers/Sec

Number of report deliveries per second, from any delivery extension.

Events/Sec

Number of events processed per second. Events that are monitored include SnapshotUpdated and TimedSubscription.

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 cannot 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 (i.e., reports that are rendered from a session snapshot).

Report Requests

Number of reports that are currently active and being handled by the report server. Use this counter to evaluate caching strategy. There might be significantly more requests than report generated.

Reports Executed/Sec

Number of reports successfully generated per second.

Total App Domain Recycles

Total number of application domain cycles after the Report Server Windows service started.

Total Cache Flushes

Total number of report server cache updates after the service started. This counter resets when the application domain recycles. See Cache Flushes/Sec.

Total Cache Hits

Total number of requests for reports processed directly from the cache after the Report Server Windows service started. This counter resets when the application domain recycles. See Cache Hits/Sec.

Total Cache Misses

Total number of times that a report could not be returned from cache after the Report Server Windows service started. This counter resets when the application domain recycles. See Cache Misses/Sec.

Total Deliveries

Total number of reports delivered by the Scheduling and Delivery Processor, for all delivery extensions. This counter resets when the application domain recycles.

Total Events

Total number of events after the Report Server Windows service started. This counter resets when the application domain recycles.

Total Memory Cache Hits

Total number of cached reports returned from the in-memory cache after the Report Server Windows service started. This counter resets when the application domain recycles.

Total Memory Cache Misses

Total number of cache misses against the in-memory cache after the service started. This counter resets when the application domain recycles.

Total Processing Failures

Total number of report processing failures that have occurred after the service started. This counter resets when the application domain recycles. 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 a synchronous process in the same thread. Under moderate or heavy load, this counter steadily increases.

Total Reports Executed

Total number of reports run.

Total Requests

Total number of reports that ran successfully after the service started. This counter resets when the application domain recycles.

Community Additions

ADD
Show:
© 2015 Microsoft