简体   繁体   English

SSRS 2008R2升级到2016年性能问题

[英]SSRS 2008R2 Upgrade to 2016 Performance Issues

We recently did an SSRS upgrade and migration going from 2008R2 to 2016 Standard SP1 on a new server. 我们最近在新服务器上进行了从2008R2到2016 Standard SP1的SSRS升级和迁移。 The migration was done with a ReportServer DB restore, so all the 2008 RDLs were copied over. 迁移是通过ReportServer数据库还原完成的,因此所有2008 RDL都被复制了。

One of the reports is taking about 20 seconds longer to render (based on the average TimeRendering value from ExecutionLog) on the new server compared to the old one. 其中一份报告比旧的报告要花费大约20秒的时间(基于ExecutionLog的平均TimeRendering值)在新服务器上进行渲染。 The report has a footer, so all the pages render at runtime. 该报告具有页脚,因此所有页面均在运行时呈现。 There is about 1800 pages worth of data, and there are many tables with groupings / logic. 大约有1800页数据,并且有许多带有分组/逻辑的表。 There are probably ways to optimize the report, but shouldn't the same report run at least as fast on my new server? 也许有多种方法可以优化报告,但是同一份报告在我的新服务器上运行的速度至少应该不那么快吗?

Below is a list of things I looked at / noticed, but at this point I don't know where else to look to see why there could be a performance difference. 以下是我查看过/注意到的事情的列表,但是在这一点上,我不知道还有什么地方可以看到为什么会有性能差异。

Old Server: 旧服务器:

  • 2008R2 2008R2
  • Report data source on same server 报告同一服务器上的数据源
  • 96GB RAM 96GB内存
  • 4 core CPU 4核CPU
  • 64 bit 2008R2 Windows Server 64位2008R2 Windows Server

New Server: 新服务器:

  • 2016 SP1 2016 SP1
  • Server on same SAN / physical location as report data source 服务器与报告数据源位于同一SAN /物理位置
  • 128 GB RAM 128 GB内存
  • 4 core CPU 4核CPU
  • 64 bit 2016 Windows Server 64位2016 Windows Server

Things I tried (none of which made a difference): 我尝试过的事情(没有任何改变):

  • Opening the RDL in VS 2015 / upgrading the RDL to new version 在VS 2015中打开RDL /将RDL升级到新版本
  • Running the report in Chrome vs IE 11 在Chrome vs IE 11中运行报告
  • Running the report on RDP 在RDP上运行报告
  • Add new report site to compatibility list in IE 将新的报告站点添加到IE中的兼容性列表
  • Running a version of the report without the footer, and the render time goes down to 1 second, but the TimeProcessing increases, so the overall runtime is still the same. 在没有页脚的情况下运行报表版本,渲染时间减少到1秒,但是TimeProcessing增加了,因此总体运行时间仍然相同。 This was very confusing... 这非常令人困惑...

Things I noticed: 我注意到的事情:

  • Old server will use more CPU than new server. 旧服务器将比新服务器使用更多的CPU。 There are other processing running, so could be due to that, but new server (ssrs only) CPU will never go over 30% usage. 还有其他处理在运行,可能是由于这个原因,但是新服务器(仅适用于ssrs)的CPU使用率永远不会超过30%。 Could this be a config somewhere? 这可以是某个地方的配置吗?

What are the data retrieval and processing times from the execution logs? 从执行日志中检索和处理数据的时间是多少? Those might point you in the right direction. 这些可能会为您指明正确的方向。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 升级sql server 2008r2到2016性能问题 - upgrade sql server 2008r2 to 2016 performance issues SSRS 2008R2 #Error的自定义值 - SSRS 2008R2 Custom value for #Error 从2008R2 / 2012/2014到ReportServer 2016的ReportServer - ReportServer from 2008R2/2012/2014 to ReportServer 2016 SQL Server 2008r2提交性能问题 - SQL Server 2008r2 Commit performance issue 报表服务在SQL2014上运行时,将报表服务器数据库从2008R2迁移到2016 - Migrating report server database from 2008R2 to 2016 while reporting service is running on SQL2014 如何在SSRS 2008r2中将第n行字段转换为图像-Report Builder 3 - How can i get the nth row field into image in SSRS 2008r2 - Report Builder 3 针对SSAS多维数据集的慢SSRS查询(SQL Server 2008R2) - Slow SSRS Query against SSAS Cube (SQL Server 2008R2) SQL Server 2008R2 SSRS报告无法连接到数据源:无法创建与数据源的连接 - SQL Server 2008R2 SSRS Reports Cannot Connect To Datasource: Cannot create a connection to data source 如何在SSRS 2008R2报表的DETAILS部分中添加分页符 - How to add page break inside the DETAILS section of SSRS 2008R2 report 我可以将SQL Server 2008r2 Express升级到SQL Server 2014 Developer Edition吗 - Can i Upgrade SQL server 2008r2 express to sql server 2014 Developer edition
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM