Performance counters MSRS 2016 Native Mode, performance objects
This article describes performance counters for the MSRS 2016 Web Service and MSRS 2016 Windows Service performance objects. These objects are part of a SQL Server 2016 Reporting Services Native Mode deployment.
Note
These performance objects 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.
The performance objects are available in the Windows Performance Monitor (Perfmon.exe). For more information, see the Windows documentation, Runtime profiling.
For information related to the SharePoint mode performance counters, see Performance counters for the MSRS 2016 Web Service SharePoint Mode and MSRS 2016 Windows Service SharePoint Mode performance objects (SharePoint mode).
In this article:
MSRS 2016 Web Service performance counters
The MSRS 2016 Web Service performance object monitors 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 2016 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 executions, whether they're still active or not. The counter is decremented as session records are removed. By default, sessions are removed after 10 minutes of no activity. |
| Cache Hits/Sec | Number of requests per second for cached reports. The requests are for re-rendered reports, not requests for reports processed directly from the cache. (See Total Cache Hits later in this article.) |
| Cache Hits/Sec (Semantic Models) | Number of requests per second for cached model. The requests are for re-rendered reports, not requests for reports processed directly from the cache. |
| 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 disk or memory caching are sufficient. |
| Cache Misses/Sec (Semantic Models) | Number of requests per second that failed to return a model from cache. Use this counter to find out whether the resources used for disk or memory caching 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 doesn't query SQL Server for cached content. |
| Memory Cache Misses/Sec | Number of times per second that reports couldn't 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 managed 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 the report server manages. |
| 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 Hits (Semantic Models) | Total number of requests for model 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 couldn't 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 Cache Misses (Semantic Models) | Total number of times that a model couldn't 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 doesn't 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 | Number of request processing errors for the report server Web service. |
| Total Rejected Threads | Total number of threads rejected for asynchronous processing, and later 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. |
MSRS 2016 Windows Service performance counters
The MSRS 2016 Windows Service performance object monitors the report server Windows service. This 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. When you set up this counter, you can apply the counter to all instances of Reporting Services or you can select specific instances.
The following table lists the counters that are included in the MSRS 2016 Windows Service performance object.
| 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're still active or not. |
| Cache Flushes/Sec | Number of cache flushes per second. |
| Cache Hits/Sec | Number of requests per second for cached reports. The requests are for re-rendered reports, not requests for reports processed directly from the cache. For more information, see Total Cache Hits later in this article. |
| Cache Hits/Sec (Semantic Models) | Number of requests per second for cached models. |
| 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. |
| Cache Misses/Sec (Semantic Models) | Number of requests per second that failed to return a model from cache. Use this counter to find out whether the resources used for disk or memory caching 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. |
| First Session Requests/Sec | Number of new report execution sessions created per 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 doesn't query SQL Server for cached content. |
| Memory Cache Misses/Sec | Number of times per second that reports can't 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 managed by the report server. Use this counter to evaluate caching strategy. There might be more requests than reports generated. |
| Reports Executed/Sec | Number of reports successfully generated per second. |
| Requests/Sec | Total number of successful requests the report server service processed per second. |
| Snapshot Updates/Sec | Total number of report execution snapshot updates 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 Hits (Semantic Models) | Total number of requests for models 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 couldn't be returned from cache after the Report Server Windows service started. This counter resets when the application domain recycles. See Cache Misses/Sec. |
| Total Cache Misses (Semantic Models) | Total number of times that a model couldn't be returned from cache after the Report Server Windows service started. This counter resets when the application domain recycles. |
| Total Deliveries | Total number of reports delivered through 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 | Number request processing errors in the report server Windows service. |
| Total Rejected Threads | Total number of threads rejected for asynchronous processing, and later 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. |
| Total Snapshot Updates | Total number of updates for report execution snapshots |
Use PowerShell cmdlets to return lists
The following Windows PowerShell script returns the counter sets where the CounterSetName starts with msr:
get-counter -listset msr*
The following Windows PowerShell script returns the list of performance counters for the CounterSetName.
(get-counter -listset "MSRS 2016 Windows Service").paths