Reporting Services performance

When I first go to the Report Manager, it takes a long time to load the web
page (15-30 seconds). After that it loads in a acceptable amount of time.
is there a way to configure it so that the page loads more quickly the first
time?
--
Message posted via http://www.sqlmonster.comI think what you will find is happening is that the Reporting Service
is "starting up" the first time you access it. We are having the same
problem and I am currently trying to find an answer. There is an
article on Microsoft's website talking about Anti-virus causing it to
restart frequently. But this doesn't seem to be that problem. The
server "stops" after a certain amount of inactivity and then takes a
while to start up when it's next accessed.
I'll post here if I find an answer.
Chris Harvie|||Here's the scoop. After a time of inactivity
First, a quick little hack. Create a very simple report, have it autoexecute
every x minutes (I do 5 minutes). I just leave this up. The delay goes away.
Then there are these suggestions from another poster which I have included
below. Personally, I had a report that I look at frequently anyway so I have
not tried this. I know my suggestion will work. If you try the below post
back on your success or failure:
Bruce Loehle-Conger
MVP SQL Server Reporting Services
>>>>>>>>>>>>>>
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
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
>>>>>>>>
<Harv013@.gmail.com> wrote in message
news:1129825242.427488.89690@.o13g2000cwo.googlegroups.com...
>I think what you will find is happening is that the Reporting Service
> is "starting up" the first time you access it. We are having the same
> problem and I am currently trying to find an answer. There is an
> article on Microsoft's website talking about Anti-virus causing it to
> restart frequently. But this doesn't seem to be that problem. The
> server "stops" after a certain amount of inactivity and then takes a
> while to start up when it's next accessed.
> I'll post here if I find an answer.
> Chris Harvie
>