sql server reporting services: First run of reports is SLOW -- sql server reporting services

Re: First run of reports is SLOW

Bruce L-C [MVP]
9/13/2005 12:08:40 PM

That is what I do, the official work around didn't work for me (IIS
configuration). If you have a report autorefresh every 5 minutes that will
keep everything ready to go.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

Re: First run of reports is SLOW

Bruce L-C [MVP]
9/13/2005 12:26:23 PM

I guess it is not "official" it is just less of a hack. I.e. adjust certain
IIS settings etc. Below is the posting from someone else describing this,
but I just have a report on my box that refreshes every 5 minutes (set this
via report properties I believe).
[quoted text, click to view]
If you are running Windows 2003 server for your IIS reportserver, then this

is a simple issue - I'll explain what happens:

The report service engine, once it is idle for more than the default 20

minutes, the worker process is shutdown.

This is controlled by IIS.

Open up the Internet Information Services (IIS) Manager

Expand the server node then the application pools.

On my IIS machine, I created an application pool dedicated to the

reportserver & reportmanager virtual webs.

But anyways, for the application pool that the reportserver is pointing to

if you left everything to their defaults will be the DefaultAppPool.

Right click the default app pool and select properties.

There are two things that are checked by default - On the recycling tab

there is a checkbox for recycling worker processes - it is currently set to

1740 minutes (29 hours). Leave it.

The other one is on the performance tab - which is the one you are

interested in changing....

See the "Idle Timeout" section and increase the number of minutes to be 8

hours a typical working day - 8*60 = 480 minutes.

Next, to be sure the "morning person" that runs the first report doesn't get

the delay, set up a schedule for either a dummy or adhoc report to fire off

like at 6am so that the report component worker processes get loaded.

I hope this helps you.

There is no need to have a report fire off every minute to keep things

alive - it is just that the report service was "unloaded" and needed to load

back up.

=-Chris

[quoted text, click to view]

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

Re: First run of reports is SLOW

John
9/13/2005 2:49:58 PM

Thanks Bruce. If the "hack" doesn't work I will just setup a report and have
it refresh every few minutes or so.

[quoted text, click to view]

Re: First run of reports is SLOW

octavius NO[at]SPAM gmail.com
9/13/2005 5:03:52 PM

I wouldn't call adjusting the properties of the app pool a "hack", but
really, "configuration".

Re: First run of reports is SLOW

Bruce L-C [MVP]
9/13/2005 11:08:12 PM

The reason I called it less of a hack is because the configuration of itself
doesn't do it. The last step was creating a subscription that ran every day.
My solution is a total hack but it is easy to do.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server reporting services group.