Extremely slow report rendering in SSRS 2008 R2 in Internet Explorer 8

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Reporting Services » Reporting Services » Extremely slow report rendering in SSRS 2008...

12 posts, Page 1 of 2

1 2 »»

Extremely slow report rendering in SSRS 2008 R2 in Internet Explorer 8

Rate Topic

Display Mode

Topic Options

Author

Message

EITCL

Posted Wednesday, November 24, 2010 6:47 AM

Valued Member

Group: General Forum Members
Last Login: Friday, June 07, 2013 5:06 AM
Points: 71, Visits: 382

With some reports that I have written for SSRS 2008 R2, the performance is problematically slow when the number of rows in the table control gets over a few hundred.

I am curious as to whether this is a problem with SSRS, or something to do with my setup. What sort of performance do any of you forum readers get? Here is a test report that I have been using.

- Create a blank report.
- Create a dataset that executes this query (it simply returns 1000 rows of dummy data)

declare @d table (id int, Result varchar(50))
declare @i int
set @i = 1000
while @i > 0
begin
insert @d values (@i, 'Data')
set @i = @i - 1
end
select Id, Result from @d

- Add a Table control
- Add the ID and Result fields to the table detail fields
- Set the "Keep together on one page if possible" option in Tablix Properties / General / Page break options
- Deploy the report to the report server

Now, when you view the report with Internet Explorer, how long does it take to render and display the report? For me, it takes 20 to 30 seconds, which is terribly slow for 1000 rows.

When you view the report with Google Chrome, how long does it take? For me, it takes about 2 seconds, which is an enormous increase over IE.

Post #1025852

Toby-126417

Posted Monday, December 06, 2010 11:53 AM

SSC Rookie

Group: General Forum Members
Last Login: Monday, July 16, 2012 2:08 PM
Points: 31, Visits: 27

Any update on your performance problem?

I have a report that produces a table with about 2000 rows. In IE8, this report renders in about 75 seconds. In Google Chrome, it renders in 17 seconds.
This is on a 2008r2 Server running SQL Server 2008r2.

Kindest Regards,

Toby

Post #1030760

EITCL

Posted Tuesday, December 07, 2010 10:20 AM

Valued Member

Group: General Forum Members
Last Login: Friday, June 07, 2013 5:06 AM
Points: 71, Visits: 382

I am still getting terrible performance. I've measured the report execution times for both Chrome and IE with varying number of rows. Please see the results below.

(The SQLServerCentral forum does not appear to keep the spaces in the table below intact, so unfortunately it looks messy and compressed)

Duration (seconds)
Rows IE Chrome
1 2 1
2 2 1
4 2 1
8 2 1
16 3 1
32 3 1
64 5 1
128 9 1
256 18 1
512 33 1
1024 67 2
2048 128 2
4096 n/a 4
8192 n/a 9
16384 n/a 18
32768 n/a 36
65536 n/a 75

As you can see, IE's performance is abysmal. The duration for IE beyond 2048 rows is not listed because it would over 2 minutes and thus unusable.

Post #1031379

jcrawf02

Posted Wednesday, December 08, 2010 7:14 AM

SSCrazy

Group: General Forum Members
Last Login: Yesterday @ 2:46 PM
Points: 2,561, Visits: 18,910

I don't know if it's a problem with IE specifically, I'll have to go test now, but we've had some issues with reports running ridiculously slow once deployed, when they run fine in BIDS. To fix that, the common workaround seems to be (after googly-moogling Wink

)to pass the parameters into your sp, then immediately store into local variables, and use the local variables to retrieve the data.

Not sure why that works, sounds sorta like parameter sniffing problems, but you're still using a variable, so no idea how that would fix the problem.

hope that helps,

Jon

---------------------------------------------------------
How best to post your question
How to post performance problems
Tally Table:What it is and how it replaces a loop

"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."

Post #1031868

EITCL

Posted Wednesday, December 08, 2010 8:26 AM

Valued Member

Group: General Forum Members
Last Login: Friday, June 07, 2013 5:06 AM
Points: 71, Visits: 382

Thanks for your input.

It is definitely not an issue with the speed of execution of the SQL code. I know this because:

1) The report is not executing a stored procedure. it is executing the T-SQL as shown in my first post.

2) When I use SQL Profiler, the T-SQL always executes in less than a second.

3) Google Chrome is able to view the same report in 2 or 3 seconds.

Post #1031920

Toby-126417

Posted Wednesday, December 08, 2010 11:14 AM

SSC Rookie

Group: General Forum Members
Last Login: Monday, July 16, 2012 2:08 PM
Points: 31, Visits: 27

Our system is using the MS ReportViewer.Webforms object to populate an ASP response page with the report contents. There is great variation in the javascript processing time between the various versions of IE. When we used the 2005 version of the reportviewer object. a report would render in about 20 seconds. When we switched to the 2010 version of the report viewer, IE8 rendering times jumped to 75 seconds. This is all using the same version of Windows and SQL Server. (2008r2 for both) I discovered that our system was causing IE8 to force IE5 emulation mode when rendering the report. Using IE7 emulation mode reduced the rendering time to 40 seconds, IE8 standards mode reduced this down to 30 seconds. These two pages helped me to sort out what was happening.
http://msdn.microsoft.com/en-us/library/cc288325(v=VS.85).aspx
http://msdn.microsoft.com/en-us/library/dd565628(VS.85).aspx#browsermodes

Kindest Regards,

Toby

Post #1032057

gus169

Posted Wednesday, March 02, 2011 5:46 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, March 14, 2012 12:26 PM
Points: 2, Visits: 34

EITCL,

I am having the same problem with one of my larger reports on SSRS 2008 R2, but when I work through your example I am not seeing the expected performance lag. Therefore here are my questions:

What version of the BID client tools were used to develop the example report? (Reason: When working with MSFT in the past, I believe they mentioned something about an issue with the keep together option and converting SQL 2005 RDLs to SQL 2008 R2. The bad conversion could be causing your IE browser to eliminate IE 5 browser.)

Have you applied any CU patches to your SSRS server? (Reason: I think CU3 has a fix a parameter bug KB#2276203.)

Can you post the RDL file?

What version of SQL is your data source connecting using? (The TSQL has to run on some platform.)

Post #1072291

DBR

Posted Thursday, March 03, 2011 3:05 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, May 09, 2013 8:24 AM
Points: 1, Visits: 90

We had the same problem with slow spped when rendering SSRS 2008 R2 reporst on IE8, particularly reports with parameters. MS do not have a fix and we are now rendering our reports using Firefox which has resolved the speed issue. One drawback with Firefox is that the back arrow does not return a sub report to the previous page.

Post #1072967

EITCL

Posted Tuesday, March 08, 2011 7:24 AM

Valued Member

Group: General Forum Members
Last Login: Friday, June 07, 2013 5:06 AM
Points: 71, Visits: 382

Hi,

Thanks for your input. The version of BIDS reported when I go to Help About is:
Microsoft Visual Studio 2008
Version 9.0.30729.4462 QFE
Microsoft .NET Framework
Version 3.5 SP1
The report RDL was developed on this version of BIDS, it hasn't been converted.

I've attached the RDL file of the report (saved as a .TXT file).

No CU patches have been applied to out server.

The SSRS is running an SQL 2008 R2 and the report is pointing to the same server.

Cheers

Post Attachments

ChooseNumberOfRows.txt (27 views, 8.50 KB)

Post #1074778

gideon 98161

Posted Thursday, April 07, 2011 4:15 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, April 07, 2011 5:55 AM
Points: 1, Visits: 2

Hi

I am having an issue with rendering a report in Internet Explorer. When the report is displayed in Print Layout in Visual Studio it displays about 500 pages which works fine, but in the Report Viewer in Internet Explorer the report defaults to the standard layout which hangs because it is trying to render all the pages into one. Is there a way around this?

Thanks in advance
Gideon

Post #1089747

« Prev Topic | Next Topic »

12 posts, Page 1 of 2

1 2 »»

Permissions