RS Lag on First Report

When I first call for a report (from URL access or called from ASP 3.0), it
takes about 10 seconds before it appears. Subsequent reports take less than
a second to appear. I'm not really sure where this lag is likely to come
from, e.g. IIS, RS, SQL Server, etc.
Where and how do I configure RS to stay "alive" longer once started (session
expiration? compile options?) and also to decrease the lag time for the
first report? Since my application is used 24x7 as far as I'm concerned it
should always be ready and quick.
Thanks.This is due to IIS.
Go to IIS Manager, under Applocation Pools node, right click
"DefaultAppPool" in which the Reporting Server work process is running,
select properties. On "Performace" tag, you will see, by default, the app
pool will shut down if > being idle for 20 min. You can extend this time to
8x60min 480min, so that the app pool will not shut down for a regular
working day. However, the first report reader of the day, will hit the
delay. You may schedule a dummy report at beginning of a work day for this.
If you have any activity at all then users should never see a delay.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Don Miller" <nospam@.nospam.com> wrote in message
news:utx6vFLHIHA.3548@.TK2MSFTNGP06.phx.gbl...
> When I first call for a report (from URL access or called from ASP 3.0),
> it takes about 10 seconds before it appears. Subsequent reports take less
> than a second to appear. I'm not really sure where this lag is likely to
> come from, e.g. IIS, RS, SQL Server, etc.
> Where and how do I configure RS to stay "alive" longer once started
> (session expiration? compile options?) and also to decrease the lag time
> for the first report? Since my application is used 24x7 as far as I'm
> concerned it should always be ready and quick.
> Thanks.
>|||Thanks.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eZ5PEWLHIHA.700@.TK2MSFTNGP05.phx.gbl...
> This is due to IIS.
> Go to IIS Manager, under Applocation Pools node, right click
> "DefaultAppPool" in which the Reporting Server work process is running,
> select properties. On "Performace" tag, you will see, by default, the app
> pool will shut down if > being idle for 20 min. You can extend this time
> to 8x60min 480min, so that the app pool will not shut down for a regular
> working day. However, the first report reader of the day, will hit the
> delay. You may schedule a dummy report at beginning of a work day for
> this.
> If you have any activity at all then users should never see a delay.
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Don Miller" <nospam@.nospam.com> wrote in message
> news:utx6vFLHIHA.3548@.TK2MSFTNGP06.phx.gbl...
>> When I first call for a report (from URL access or called from ASP 3.0),
>> it takes about 10 seconds before it appears. Subsequent reports take less
>> than a second to appear. I'm not really sure where this lag is likely to
>> come from, e.g. IIS, RS, SQL Server, etc.
>> Where and how do I configure RS to stay "alive" longer once started
>> (session expiration? compile options?) and also to decrease the lag time
>> for the first report? Since my application is used 24x7 as far as I'm
>> concerned it should always be ready and quick.
>> Thanks.
>