Comments:

Flat Nested Threaded Embedded

Oldest First Newest First

Author	Thread:
Jens	Reporting services very slow on first report Posted: Friday, May 26, 2006 7:16 AM (GST) Here is some more information.  If anyone can help I sure would appreciate it.   I am experimenting with a very simple (just two fields) RS 2000 report.  Reporting Services is setup as part of the DefaultAppPool.  I discovered that the first time I access **either** a report through the "web service", or just the Report Manager manually through a browser, it takes a long time to load.  After a 20 minute period of inactivity the same problem would occur. On the DefaultAppPool Properties dialog box I did the following... On the Recycling tab: 1. I UNchecked "Recycle worker process (in minutes)" 2.  I checked "Recycle worker process at the following times" and set it to 03:00 (3 AM) On the Performance tab: 1.  I UNchecked "Shutdown worker process after being idle for..."   Someone suggested I setup a subscription so that a "dummy" report would run after the worker process was recycled.  I set up a report to run at 03:05 (5 minutes after the worker process recycle).  The report does run and copies itself to a directory....  But,.... I'm still having the same problem.  I tried setting the dummy report to run every hour.  I runs every hour, but I still have the same "first access" problem.   What can/should I do?  It is not acceptable to have a long delay after the worker process is recycled.   Is it important to recycle the worker process, or can I just have it run indefinitely?   If the worker process should be recycled, can I have a macro run so it will "spin up" the worker process? Thank you.
dribar	Reporting services very slow on first report Posted: Monday, January 08, 2007 1:56 PM (GST) Did you ever get this one figured out?   I have gone through the exact steps -- even have an subscription to a report that runs on the 15 minutes,  but the first user to get a report (from an asp.net page) times out....   Call me if need be or email. Thanks.   Dan Ribar 800-995-4827 dribar@1stGuard.com
dribar	Reporting services very slow on first report Posted: Saturday, January 27, 2007 11:38 AM (GST) The solution is pretty simple actually.    Microsoft does a great job of getting technologists excited about new technologies like the 'Web Gardens' in IIS 6.     The problem was two fold -- but all in IIS.   First,  I had bumped the web garden setting up to '8' thinking that it would spread the processing out.  Maybe if I was getting a gazillion hits a day, but the reality was that each worker process had to spin up.  So if I started one browser and tried to run a report,  it would spin #1 up.  If I opened another browser, it would spin up #2 and so on.     Second was that I had the worker processes 'recycling' on idle.  Which in a web garden of 8 would really cause delays.  By the time I got to spinning up #7 or #8,  #1 had already spun back down.... ARGHHHH.   Solution was to put worker processes back on '1',  and turn off the recyling.   Now it stays up all the time,  and responds almost instantly.   Good Luck.     Dan Ribar
GregAllan	Reporting services very slow on first report Posted: Monday, January 29, 2007 5:33 PM (GST) Thanks Dan, I've been watching this thread for a long time and I'm going to try your technique. Where is this "web garden setting"? I'm looking in IIS 6.0 Also, is there a test I can run to verify the improvement in server response? Thanks, Greg
dribar	Reporting services very slow on first report Posted: Monday, January 29, 2007 5:55 PM (GST) In IIS manager, expand on your server,  then look under "Application Pools".   By default,  there should only be one called DefaultAppPool.   If you want to preserve the default,  just add a new one by right clicking on the AppPools folder.   So right click 'properties' on the app pool and then check these spots:   Recycling Tab: I only have the default top one checked for recycle after 1740 minutes.  My site has enough activity to keep this one spun up.   Performance Tab: Recycle UNCHECK this one.  It is the main culprit.  Then at the bottom is the web garden settings that I have set to one.  All the rest is turned off for me.   Health and Identity tabs I left at default.   This made a huge difference for me.  Not sure about a report except that when I run reports that are SQL-based,  the site is almost instantaneous including the generation of PDF output.  Compare that with 45 seconds of spin-up time when they were shutting down on idle.   Good Luck.   Dan Ribar
codezilla	Reporting services very slow on first report Posted: Tuesday, November 13, 2007 2:05 AM (GST) I had the same problem. The reason is that the application domain times out every 20 mins if there is no activity, the first request after the timeout can force a recompile and reload of cache. Changing some settings in the machine.config file will solve the problem; unfortunately for me my hosting provider would not allow me to make this change. I found this utility to be useful. http://www.spikesolutions.net/ViewSolution.aspx?ID=c2b7edc0-5de1-4064-a432-05f6eded3b82 Essentially it "Pings" my home page every few mins so the application domain does not time out. The utility can also be configured to ping more than one page so that auxiliary pages are fast too.
nickidw	Reporting services very slow on first report Posted: Thursday, June 12, 2008 8:18 AM (GST) It is all good to have a workaround, but do we know what is the *real* reason behind the slow startup, and can we do anything about that? Tweaking the AppPool settings will make a difference, but will not help with the slow startup the first time some accesses the site. I'm also annoyed by the slow first time access, and would like to make it faster if possible. Any ideas?
GregAllan	Reporting services very slow on first report Posted: Thursday, June 12, 2008 5:47 PM (GST) Here's another blog on the subject: http://blogs.msdn.com/lukaszp/archive/2007/09/18/keeping-your-report-servers-awake-or-no-more-waiting-for-report-server-to-startup.aspx
Vilmis	Reporting services very slow on first report Posted: Tuesday, June 17, 2008 3:13 AM (GST) http://www.microsoft.com/technet/prodtechnol/sql/2005/pspsqlrs.mspx "If performance is slow on the first Web service access after a period of no activity, disable the idle time-out on the Performance tab in the Application in IIS Manager."   It won't help with first time, but at least it runs faster if nobody runs reports for period of time.