Using Performance console

Performance console monitors specific performance counters enabling you to estimate system requirements, create a performance baseline, monitor application performance, and measure whether hardware upgrades and other changes to your system have the desired impact on performance.

You can use the Performance console to monitor specific performance counters. These counters enable you to:

  • Estimate system requirements needed to support an anticipated workload
  • Create a performance baseline to measure the impact of configuration changes or application upgrades
  • Monitor application performance under certain loads, whether real or artificially generated<
  • Verify that hardware upgrades have the desired impact on performance
  • Validate that changes made to your system configuration have the desired impact on performance

    Reporting Services includes two performance objects: RS Web Service, which monitors report server performance, and RS Windows Service, which monitors scheduled operations and report delivery.

    The RS Web Service 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 Reporting Services Web service.

    The RS Windows Service 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.

    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 adding a counter. For more information about using Performance console and adding counters, see the Microsoft Windows product documentation.

    Use performance monitoring tools to monitor report server performance by evaluating server activity, observing trends, diagnosing system bottlenecks, and gathering data that can help you determine whether the current system configuration is adequate. To access Performance console, follow these steps:

    1. Choose Start➪Performance from the Administrative Tools menu to open the System Monitor. The System Monitor appears.

    2. Add Counters to the list by right-clicking in the grid showing various counters in the view and selecting Add Counters from the menu that appears (see Figure 14-1).

    3. Select the RSWeb service counters. In the Add Counters dialog, select RSWeb Service from the drop- down box for the Performance object. Then click the All Counters radio button. Finally, click OK.

    4. View the System Monitor. You see all RD Web counters below the chart displayed on the performance monitor, each corresponding to a unique color on the display.

    I describe the counters available for monitoring in Table 14-1.

    Above figure 14-1: Security roles in the Object Explorer with the task permission for the Browser role on the right side.

    Table 14-1 Report Services Performance Counters
    Counter Name Description
    Active Sessions Count of all browser sessions generated from report subscriptions (active or not).
    Cache Hits/Sec Number of requests per second for re-rendered cached reports.
    Cache Misses/Sec Number of requests per second that failed to return a report from cache to determine whether the resources used for caching (disk or memory) are sufficient.
    First Session Requests/Sec Number of new user sessions 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 (no query of SQL Server for cached content).
    Memory Cache Misses/Sec Number of times per second reports could not be retrieved from the in-memory cache.
    Next Session Requests/Sec Number of reports rendered from a session snapshot.
    Report Requests Number of reports currently active and being handled by the report server.
    Reports Executed/Sec Number of successful report executions per second.
    Requests/Sec Number of requests (all types) per second made to the report server.
    Total Cache Hits Total number of requests for reports from the cache after the service started.
    Total Cache Misses Total number of times a report could not be returned from the cache after the service started.
    Total Memory Cache Hits Total number of cached reports returned from the in- memory cache after the service started.
    Total Memory Cache Misses Total number of cache misses against the in-memory cache after the service started.
    Total Processing Failures Total number of report processing failures that have occurred after the service started.
    Total Rejected Threads Total number of data processing threads (one data source per thread) in excess of capacity, requiring serial processing.
    Total Reports Executed Total number of reports that ran successfully after the service started.
    Total Requests Total number of all requests made to the report server after the service started.

    The previous tip was excerpted from Chapter 14, 'Optimizing Report Performance,' from the book "Microsoft SQL Server 2005 Reporting Services for Dummies" by Mark Robinson, courtesy of Wiley Publishing. Click here for the complete collection of book excerpts.

  • This was first published in July 2006

    Dig deeper on Microsoft SQL Server Performance Monitoring and Tuning

    Pro+

    Features

    Enjoy the benefits of Pro+ membership, learn more and join.

    0 comments

    Oldest 

    Forgot Password?

    No problem! Submit your e-mail address below. We'll send you an email containing your password.

    Your password has been sent to:

    SearchBusinessAnalytics

    SearchDataCenter

    SearchDataManagement

    SearchAWS

    SearchOracle

    SearchContentManagement

    SearchWindowsServer

    Close