Report Manager Start Up

I believe that I read somewhere in the past that there was a setting in IIS
that you could change in order to have the Report Manager not recompile on
first request. As we all know it takes an unusually long time for Report
Manager to start up the first time you call the application. I would like to
know if there is a setting or change that I can make in order to have Report
Manager Load faster.
Thanks,
--
Andrew
MCSA,MCDBAHi,
I believe the setting you are looking for is the "Shutdown worker processes
after being idle for..." on the Performance tab of the application pool that
the Reports virtual directory is assigned to.
See old post below for details:
>>>>>>>>>>
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
>>>>>>>>>>
"Andrew" wrote:
> I believe that I read somewhere in the past that there was a setting in IIS
> that you could change in order to have the Report Manager not recompile on
> first request. As we all know it takes an unusually long time for Report
> Manager to start up the first time you call the application. I would like to
> know if there is a setting or change that I can make in order to have Report
> Manager Load faster.
> Thanks,
> --
> Andrew
> MCSA,MCDBA|||Chris,
Thanks, that is exactly what I was looking for.
--
Andrew
MCSA,MCDBA
"Oweste" wrote:
> Hi,
> I believe the setting you are looking for is the "Shutdown worker processes
> after being idle for..." on the Performance tab of the application pool that
> the Reports virtual directory is assigned to.
> See old post below for details:
> >>>>>>>>>>
> 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
> >>>>>>>>>>
>
> "Andrew" wrote:
> > I believe that I read somewhere in the past that there was a setting in IIS
> > that you could change in order to have the Report Manager not recompile on
> > first request. As we all know it takes an unusually long time for Report
> > Manager to start up the first time you call the application. I would like to
> > know if there is a setting or change that I can make in order to have Report
> > Manager Load faster.
> >
> > Thanks,
> >
> > --
> > Andrew
> > MCSA,MCDBA