Monday, January 21, 2013 11:02 AM
Hi we are experiencing a performance issue when a report is being run within the Report Viewer Control in ASP.NET. We are using the report viewer in Remote mode.
We are using SQL Server 2008 R2, Visual Studio 2010 and ASP.NET, .NET FrameWork v4.
We have 3 Servers: Webserver, Reporting Services Server and a Database Server. They are all virtual machines on the same virtual network.
The stored procedures execute in a very short period of time. Less than 5 seconds
When the report is executed via the Report Manager (RDP'ed onto the reporting server). It executes in 30 seconds (which is fine for this report). When the same report is Executed from within the ASP.NET page using the Report Viewer Control on the same machine, it takes around 5 minutes to run - which is not ok.
I have checked the Network/CPU/IO on the Reporting server, it appears that after a short while, the CPU is hit for a few seconds, after that there is a long period of Network Traffic from the SQL Server to the Report Server - 12-15mbps for around 5 minutes, After which the report is being rendered by Internet Explorer. This Network Traffic does not occur when the report is being executed in Report Manager, it just returns straight away. The virtual network also appears to be fine, when copying a file between the two servers the throughput is fine.
If you look at the execution log table on the ReportServer database, it claims to have finished within 15-20 seconds on both executions! 5 seconds data retrieva, 6 Seconds Processing, 6 Seconds Rendering. The question is what is different between the two executions? And what can we do about it?
The Reporting Services databases are both on the SQL server (Not local to the Reporting Services Server), however, we do have a development environment where it is on the same box as the Reporting Services Server, yet this still has the same issue.
How can Report Manager execute it perfectly and yet it takes ages using Report Viewer?
Tuesday, January 22, 2013 1:31 PM
Unfortunately this doesnt really help. The report runs fast enough in Report Manager, we just want it to run We dont really need the report to run any quicker (tho we have made some more improvements to the report to make it quicker).
It seems like rolling back to V9 of the Report View Control has fixed this issue.
Wednesday, January 23, 2013 7:00 AMModerator
This may be a known performance issue with ReportViewer control 2010 which has been fixed in ReportViewer control 2010 SP1. Here, I suggest that you install the ReportViewer control 2010 SP1 and its update in your development environment first:
- Microsoft Report Viewer 2010 SP1 Redistributable Package
- Update for Microsoft Visual Studio 2010 Service Pack 1 Report Viewer (KB2549864)
Hope this helps.
If you have any feedback on our support, please click here
TechNet Community Support
Thursday, January 31, 2013 3:07 PM
I tried installing this service pack and it did not fix it (I simply copied the reportviewer 10 SP1 DLLs on to the server). Currently we are in the process of rolling back to V9.
Although this caused other issues including the Date Picker not working, Hyperlinks being displayed with the wrong font and unwanted scroll bars!