0

We have a sharepoint portal running SSRS reports for our customers.

The reports themselves dont take that long to render, however the page requests take over 10-15 seconds which is simply unacceptable from a customers perspective.

How can I overcome this? Is there anything in particualr I can do to improve performance?

Improve this question

1 Answer 1

Reset to default
1

If you're running this using SharePoint integrated mode that would be one possible explanation. What versions of SharePoint and SSRS are you running? We switched everything to Native Mode and it runs much quicker. Microsoft has tried addressing this with Sql Server 2012 and a new report viewer control, but our experience was native mode was still quicker. You will lose some of the convenience of the integration, like managing security in one place, but for us the performance concerns outweighed the convenience.

There are other examples but this is a good one of someone else who had the same problem:

http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/4ed01ff4-139a-4eb3-9e2e-df12a9c316ff

Hope that helps.

Improve this answer
6
  • Thanks for the post! We are running SQL2008 R2 with SP1 and the Reporting Services Add-in (SP1 version ending in .2500). When you say your performance got better could you give me a number/precentage in performance increase please.
    – user7400
    Commented Jan 15, 2013 at 20:45
  • I don't have any official numbers since this is not an in-house application but a product we sell ( so every client environment is different ). However, I would say in my local dev box running two ssrs reports simultaneously on the same page went from 20-30 seconds to 5-10 seconds on average. There are obviously a lot of factors like the amount of data, the report type, etc. However, if the report runs fine in BIDS, it will probably run just as well in Native Mode.
    – trpeel
    Commented Jan 15, 2013 at 21:24
  • 2 things here: 1. The sharepoint page request itself takes voer 20s (due to the JIT lag caused on every first hit) 2. The reports render slow the first time around till things get cached and then it all speeds up (when I say speeds up, I mean 2-5 seconds on any report in integrated mode) Im really looking to deal with the "Warm up" aspect of the application. Everything else seems to be looking decent enough. Thanks for all the input! Let me know if you do come across any related info.
    – user7400
    Commented Jan 15, 2013 at 21:33
  • We created a timer job that pings the report pages to keep them alive. I've seen some similar timer jobs online that you can probably search for. If you have trouble finding them let me know.
    – trpeel
    Commented Jan 16, 2013 at 23:15
  • I found a warm up script which seems to achieve something similar: blog.karstein-consulting.com/2011/08/03/… but did not see any difference in first request performance Could you run me through the timer job setup that you'll have in place please?
    – user7400
    Commented Jan 18, 2013 at 14:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.