Monitoring Report Server Performance
Use performance monitoring tools to monitor report server performance to evaluate server activity, watch trends, diagnose system bottlenecks, and gather data that can help you determine whether the current system configuration is sufficient. To tune server performance, you can specify how often to recycle the report server application domain. For more information, see Configuring Available Memory for Report Server Applications.
Use a combination of technologies and tools to get comprehensive information about how the system is performing. Microsoft Windows Server operating systems provide performance information through the following tools:
Task Manager provides information about programs and processes running on your computer. You can use Task Manager to monitor key indicators of your report server's performance. You can also assess the activity of running processes and view graphs and data on CPU and memory usage. For information about using Task Manager, see the Microsoft Windows product documentation.
You can use Performance Console and Event Viewer to create logs and alerts about report processing and resource consumption. For information about Windows events that are generated by Reporting Services, see Windows Application Log. For information about Performance Console, see "Windows Performance Counters" later in this topic.
SQL Server utilities also provide information about the report server database and temporary databases used for caching and session management. For more information, see Evaluating Performance.
Monitoring specific performance counters enables you to:
Estimate system requirements needed to support a predicted workload.
Create a performance baseline to measure effect of configuration changes or application upgrades.
Monitor application performance under certain loads, whether real or artificially generated.
Verify that hardware upgrades have the desired effect on performance.
Validate changes that were made to the system configuration have the desired effect on performance.
SQL Server 2008 Reporting Services includes the following performance objects:
MSRS 2008 Web Service 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. These counters are reset whenever ASP.NET stops the Report Server Web service.
MSRS 2008 Windows Service to monitor scheduled operations and report delivery. This performance object includes a collection of counters used to track report processing that is initiated through scheduled operations. Scheduled operations include subscription and delivery, report execution snapshots, and report history.
ReportServer:Service to monitor HTTP-related events and memory management. This performance object is new in SQL Server 2008 Reporting Services, and it provides counters that were included with Internet Information Services (IIS) and ASP.NET in previous versions of Reporting Services. These counters are specific to Reporting Services, and they track HTTP-related events for the report server, such as requests, connections, and logon attempts. This performance object also includes counters related to memory management.
If you have multiple report server instances on a single computer, you can monitor the instances together or separately. Choose which instances to include when you add a counter. For more information about using Performance Console (perfmon.msc) and adding counters, see the Microsoft Windows product documentation.
Custom Reporting Services performance counters are provided only for MSRS 2008 Web Service, MSRS 2008 Windows Service, and ReportServer:Service. The following performance objects provide additional performance monitoring data for the report server.
.NET CLR Data and .NET CLR Memory
Report Manager uses ASP.NET performance counters. For more information, see "Improving .NET Application Performance and Scalability" on MSDN.
Add the Elapsed Time and ID Process performance counters for a ReportingServicesService instance to track process uptime by process ID.
In addition to the Reporting Services performance objects, you might also want to configure SharePoint events if you are running a report server in SharePoint integrated mode and have configured your reporting environment to use Windows SharePoint Services (WSS) 3.0 or Office SharePoint Server (MOSS) 2007. In this section, use the Events for a Report Server in SharePoint Integrated Mode to review diagnostic events that might provide useful information if your reporting environment is integrated with SharePoint. For more information about estimating performance in various SharePoint deployments, see Estimate performance and capacity requirements (Office SharePoint Server) on Microsoft TechNet.