SSRS "timerendering" is very slow
Posted on 2009-02-18
We have several reports setup in SSRS 2005 that are running very slow.
Through looking at the SSRS logs in the ReportServer database, we've deduced it is primarily the TimeRendering that is, by far, the slowest part of the report generation process. TimeDataRetrieval and TimeProcessing combined may only be a second or two, whereas TimeRendering can sometimes be ten or twenty times that.
Here's an example:
Not an abnormally huge number of rows, I don't understand why the report is taking so long to render. We've tried moving the report server to a different, much more powerful server with little affect on rendering time.
During the report generation, w3wp.exe on the SSRS server is pretty much pegged out the processor.
I haven't examined the .RDL files closely yet, I'm not super familiar with the report designer and "best practices" for designing reports. Can anyone give me some insight on what might be causing the render portion to take so long? Anything I should look out for or change in terms of design of the RDL's?