ssrs筛选器_SSRS ReportServer:服务性能计数器指南

ssrs筛选器

SSRS性能计数器 (SSRS performance counters)

Measurements of the Reporting Services service (SSRS) monitoring cycle show which resources the reporting process consumes, and also, specific sets of counters show the particular type of the reporting process deployment in use, Native and SharePoint mode. The entire reports processing occurs in the Report Server, which is the core element of SSRS architecture, and among all features, collaboration with SharePoint platform is the most crucial, because of advantages of report processing and generating reports for SharePoint components.

对Reporting Services服务(SSRS)监视周期的度量显示了报告过程消耗的资源,并且特定的计数器集还显示了正在使用的报告过程部署的特定类型(本机和SharePoint模式)。 整个报表处理都在报表服务器中进行,报表服务器是SSRS体系结构的核心元素,在所有功能中,与SharePoint平台的协作是最关键的,因为报表处理和为SharePoint组件生成报表的优势。

The SSRS service itself has many performance counters, and that is the reason there are three standardized groups of SSRS performance objects:

SSRS服务本身具有许多性能计数器,因此这是三个标准化的SSRS性能对象组的原因:

  1. MSRS 2011 Web Service and MSRS 2011 SharePoint Mode Web Service – these performance objects with their specific performance counters monitor report server performance and its processing on behalf of interactive report viewing tasks.

    MSRS 2011 Web服务MSRS 2011 SharePoint模式Web服务 –这些性能对象及其特定的性能计数器代表交互式报表查看任务监视报表服务器性能及其处理。

  2. MSRS 2011 Windows Service and MSRS 2011 Windows Service SharePoint Mode – to monitor scheduled operations and report delivery, these two groups of performance counters track the operations like subscription, delivery, snapshots of report execution, and history of reports processing.

    MSRS 2011 Windows ServiceMSRS 2011 Windows Service SharePoint模式 –这两组性能计数器监视预定的操作和报告的交付,跟踪订阅,交付,报告执行的快照以及报告处理历史等操作。

  3. ReportServer:Service and ReportServerSharePoint:Service – these performance counters are the main topic of this article.

    ReportServer:ServiceReportServerSharePoint:Service –这些性能计数器是本文的主题。

SSRS ReportServer:服务性能计数器 (SSRS ReportServer:Service performance counters)

Performance counters for ReportServer:Service and ReportSharePointServer:Service, as SharePoint part of ReportServer:Service, display specific measurements related to HTTP activity, which regards the web-related events of the Report Server, like requests, connections, logon attempts, and also the memory management events. In reporting process, some of the resources of the Report server will be dedicated to SharePoint components.

作为ReportServer:Service的 SharePoint部分, ReportServer:ServiceReportSharePointServer:Service的性能计数器显示与HTTP活动相关的特定度量,这些度量涉及Report Server与Web相关的事件,例如请求,连接,登录尝试以及内存管理事件。 在报告过程中,报告服务器的某些资源将专用于SharePoint组件。

There are seven categories of reporting services performance counters:

报告服务绩效计数器分为七类:

  1. Connections

    连接数
  2. Bytes

    字节数
  3. Errors

    失误
  4. Logon

    登入
  5. Memory

    记忆
  6. Requests

    要求
  7. Tasks performance counters

    任务性能计数器
  1. Connections performance counter

    连接性能计数器

    • Active connections: this counter shows the number of active connections on the server at the certain time point.

      活动连接 :此计数器显示特定时间点服务器上的活动连接数。

    Note: The value of this performance counter displays as a numeric, it is based on the number of allowed requests (see under Requests performance counters) and there is no default maximum number of connections. Even though there is no limit, too many connections sometimes can overwhelm the memory resources (if user requested too many complex reports processing), and that can interrupt the flow of the reporting process itself.

    注意 :此性能计数器的值显示为数字,它基于允许的请求数(请参阅“ 请求性能计数器”下的内容 ),并且没有默认的最大连接数。 即使没有限制,太多的连接有时也会使内存资源不堪重负(如果用户请求太多复杂的报表处理),这可能会中断报表过程本身的流程。

  2. Bytes performance counters

    字节性能计数器

    • Bytes Received total and Bytes sent total: these counters show the number of bytes received and sent in total by both Report Manager and the Report Server. Values of these counters show as the actual bytes received/sent (46.137.344, which is 44 MB, e.g.).

      接收的字节总数和发送的字节总数 :这些计数器显示报表管理器和报表服务器的接收和发送的字节总数。 这些计数器的值显示为实际接收/发送的字节数( 例如46.137.344 ,即44 MB)。

    • Bytes received/sec and Bytes sent/sec: they display the number of bytes received/sent by the server per second. (2.097.152/s, which is 2 MB/s, e.g.).

      每秒接收的字节数每秒 发送的字节数它们显示服务器每秒接收/发送的字节数。 ( 2.097.152 / s ,例如2 MB / s)。

    Note: The measurement of this counter updates after the transfer is done, so its value remains at 0 and then the value shows as increased.

    注意 :此计数器的测量在传输完成后更新,因此其值保持为0,然后该值显示为增加。

  3. Errors performance counters

    错误性能计数器

    • Errors total: this counter displays the number of errors received in total, during the processing of HTTP requests.

      错误总数 :此计数器显示在处理HTTP请求期间总共收到的错误数。

    • Errors/sec: as the previous, this counter shows the number of errors received per second.

      错误/秒 :与以前一样,此计数器显示每秒接收的错误数。

    Note: These both measurements (displayed as a numeric value, or numeric value/s, 6 or 6/s, e.g.) can show the website issues including level 400 and level 500 errors.

    注意 :这两个度量(例如,以数字值或每秒66 / s的数值显示)可以显示网站问题,包括400级和500级错误。

  4. Logon performance counters

    登录性能计数器

    • Logon Attempts Total and Logon Successes Total: these performance counters show the number of logon attempts and logon successful attempts made from Report Services Windows authentication types.

      登录尝试总数登录成功总数 :这些性能计数器显示通过Report Services Windows身份验证类型进行的登录尝试和成功登录尝试的次数。

    • Logon Attempts/sec and Logon Successes/sec: they display the number of logon attempts and successful logons per second.

      登录尝试次数/秒登录成功次数/秒 :它们显示每秒的登录尝试次数和成功登录次数。

    Note: If the value of Logon Attempts Total and/or Logon Successes Total is 0, Custom (User) authentication is in use. These counters give an insight of how many logon attempts were successful or unsuccessful while logging to the server.

    注意 :如果“登录尝试总数”和/或“登录成功总数”的值为0 ,则使用自定义(用户)身份验证。 通过这些计数器,可以了解登录到服务器时成功或不成功的登录尝试次数。

  5. Memory performance counters

    内存性能计数器

    • Memory Pressure state: this counter shows the current stadium of memory resources of the server. There are five values of measurement:

      内存压力状态 :此计数器显示服务器当前的内存资源范围。 有五个测量值:

      1 – Memory is not under pressure
      2 – Low level of memory pressure
      3 – Medium level of memory pressure
      4 – High level of memory pressure
      5 – Memory is extremely under pressure

      1 –内存没有压力
      2 –低内存压力
      3 –中等压力
      4 –高内存压力
      5 –内存压力很大

    • Memory Shrink amount: this counter displays the number of bytes, requested by the server to shrink the memory in use. A value of measurement displays as number of bytes (63.963.136, which is 61 MB, e.g.)

      内存缩减量 :此计数器显示服务器请求缩减正在使用的内存的字节数。 测量值显示为字节数( 63.963.136 ,例如61 MB)

    • Memory Shrink Notifications/sec: it displays the number of notifications that the server triggered in the last second to shrink the memory in use. The value of this counter indicates how often the server memory is pressurized. If the value is 0, memory is not pressurized at particular moment.

      内存缩减通知/秒 :它显示服务器在最后一秒触发以缩减正在使用的内存的通知数。 此计数器的值指示对服务器内存加压的频率。 如果值为0 ,则在特定时刻内存不加压。

    Note: If performance issues occur, the combination of Active connections and this performance counter can help in determination of the potential bottleneck. Also, these performance counters are specific for the ReportSharePointServer:Service performance object.

    注意 :如果发生性能问题,则将活动连接和该性能计数器结合使用可以帮助确定潜在的瓶颈。 同样,这些性能计数器特定于ReportSharePointServer:Service性能对象。

  6. Requests performance counters

    要求性能计数器

    • Requests Disconnected and Requests Not Authorized: these performance counters show the number of requests which failed because of a communication failure and the number of requests, and it triggers the HTTP 401 status code.

      请求断开连接未授权请求 :这些性能计数器显示由于通信失败而失败的请求数和请求数,并触发HTTP 401状态码。

    • Requests Executing: this performance counter displays the number of requests in process at the certain time point.

      正在执行的请求 :此性能计数器显示在特定时间点处理中的请求数。

    • Requests Rejected: it displays the number of requests which were not processed due to insufficient server resources. It also returns a HTTP 503 status code (Server is busy).

      拒绝的请求数:它显示由于服务器资源不足而未处理的请求数。 它还返回HTTP 503状态代码(服务器正忙)。

    • Requests Total: this counters shows the total number of requests logged by the report server from the report manager since startup (or last reboot of the machine). It also summarizes requests sent to Report Manager and those sent from Report Manager to the report server.

      请求总数 :此计数器显示自启动(或计算机的最后一次重新启动)以来,报告服务器从报表管理器记录的请求总数。 它还汇总了发送到报表管理器的请求以及从报表管理器发送到报表服务器的请求。

    • Requests/sec: it shows the number of processed requests per second. This value represents the current throughput of the application.

      Requests / sec :显示每秒处理的请求数。 该值表示应用程序的当前吞吐量。

    Note: For a single user, maximum number of allowed requests is 20, by default. Also, value 0 indicates no limit to the number of connections. However, this value can be preset with RSReportServer.config feature.

    注意 :对于单个用户,默认情况下,允许的最大请求数为20 。 此外,值0表示对连接数没有限制。 但是,可以使用RSReportServer.config功能预设此值。

  7. Tasks performance counters

    任务性能计数器

    • Tasks Queued: this performance counter displays the number of requests currently waiting to be processed. Each of the requests made to the report server corresponds to one or more tasks, and this counter is including only tasks that are active at certain time point. Value of this counter displays as a numeric (排队的任务 :此性能计数器显示当前等待处理的请求数。 向报表服务器发出的每个请求都对应一个或多个任务,并且此计数器仅包括在特定时间点处于活动状态的任务。 此计数器显示值作为数字( 7, if 7 tasks are queued, e.g.) 图7,如果7个任务排队,例如)

    Note: Deep insight on the server’s activity can be done by looking through measurements from Tasks Queued Requests Queued, Requests Executing and Requests Rejected performance counters.

    注意 :可以通过查看“已排队的任务” ,“正在执行的 请求”和“已拒绝的请求”性能计数器中的度量来深入了解服务器的活动。

有用的链接: (Useful links:)

翻译自: https://www.sqlshack.com/ssrs-reportserver-service-performance-counters-guide/

ssrs筛选器

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值