Reputation: 11
Am trying to figure out why our SSRS execution is so slow. The home page takes about 10 seconds to load/refresh and reports take 12-15 seconds just to render to the 'Enter Parameter Settings' stage.
I have created a report with a single text box - no data connections - no data-set - so ZERO database access and yet it still consistently takes 12 seconds to render - A SINGLE TEXT BOX WITH NO DATABASE ACCESS! Every single click in the report engine takes 12-15 seconds to respond to - which makes it quite painful to work with real data.
The database and an IIS installation is also included on the same machine - but they are only accessed by a couple of users (nothing public) - so the machine isn't under a lot of load. All other services on this box are responding quickly: The IIS installation is serving up web-service requests quickly and responsively - within a split-second. And all database queries are running at a very speedy rate - consistent with the generous hardware on this box.
It doesn't seem to be related to 'First Request' spooling up - this is happening on all requests.
All the other answers relating to SSRS speed issues seem to be related to database query tuning and parameter handling - but this 'no-data' test report seems to be pointing to something wrong within the SSRS installation/execution itself.
Any help?
Upvotes: 1
Views: 632
Reputation: 119
I would run Report Manager locally from the server and have Task Manager up to monitor the activity of the server to identify possible server resource issues and rule out network/client connectivity issues.
Even though you are using a "dummy" report with no DataSource, IIS still has to talk to SQL Server to get report metadata. I would check to make sure all the SSRS components are talking to each other by using the Reporting Services Configuration Tool for your specific SQL version.
Upvotes: 2