Opening RS HomePage is Extermly slow! Please help.

When a client types in the homepage of the RS it takes minutes to open
instead of seconds. It is running on a W2K3 machine with SQL 2000 and the
clients are a mix of XP and 2K Pro. Any advice would be great. Oh this also
happens on the server itself.
Once you open it once it opens in seconds from then on until you logoff and
back on to the pc again. Then it is slow again.
Thanks!This was discussed in the forum several months ago. You can find the
discussion by going to
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx and do a
search on the text "First Time Delay on Client Systems".
"Andy Jones" <ajones@.rheemac.com> wrote in message
news:eJAhsvihFHA.2424@.TK2MSFTNGP09.phx.gbl...
> When a client types in the homepage of the RS it takes minutes to open
> instead of seconds. It is running on a W2K3 machine with SQL 2000 and the
> clients are a mix of XP and 2K Pro. Any advice would be great. Oh this
also
> happens on the server itself.
> Once you open it once it opens in seconds from then on until you logoff
and
> back on to the pc again. Then it is slow again.
> Thanks!
>|||Which specific post? There are so many, I'm not sure which one applies...
"Vince Sefcik" wrote:
> This was discussed in the forum several months ago. You can find the
> discussion by going to
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx and do a
> search on the text "First Time Delay on Client Systems".
> "Andy Jones" <ajones@.rheemac.com> wrote in message
> news:eJAhsvihFHA.2424@.TK2MSFTNGP09.phx.gbl...
> > When a client types in the homepage of the RS it takes minutes to open
> > instead of seconds. It is running on a W2K3 machine with SQL 2000 and the
> > clients are a mix of XP and 2K Pro. Any advice would be great. Oh this
> also
> > happens on the server itself.
> >
> > Once you open it once it opens in seconds from then on until you logoff
> and
> > back on to the pc again. Then it is slow again.
> >
> > Thanks!
> >
> >
>
>|||Here is a suggestion from Chris that worked for him. I was unsuccessful with
this. What I do is I have a simple report that I have automatically refresh
every 5 minutes (set this in Report Properties).
>>>>>>>>>>
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
>>>>>>>>>>>>>>>'
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"MustangDJB" <MustangDJB@.discussions.microsoft.com> wrote in message
news:E12C4DCA-AF89-4770-9649-6E0775FA42ED@.microsoft.com...
> Which specific post? There are so many, I'm not sure which one
> applies...
> "Vince Sefcik" wrote:
>> This was discussed in the forum several months ago. You can find the
>> discussion by going to
>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx and do
>> a
>> search on the text "First Time Delay on Client Systems".
>> "Andy Jones" <ajones@.rheemac.com> wrote in message
>> news:eJAhsvihFHA.2424@.TK2MSFTNGP09.phx.gbl...
>> > When a client types in the homepage of the RS it takes minutes to open
>> > instead of seconds. It is running on a W2K3 machine with SQL 2000 and
>> > the
>> > clients are a mix of XP and 2K Pro. Any advice would be great. Oh this
>> also
>> > happens on the server itself.
>> >
>> > Once you open it once it opens in seconds from then on until you logoff
>> and
>> > back on to the pc again. Then it is slow again.
>> >
>> > Thanks!
>> >
>> >
>>|||Thank you! That does appear to help.
"Bruce L-C [MVP]" wrote:
> Here is a suggestion from Chris that worked for him. I was unsuccessful with
> this. What I do is I have a simple report that I have automatically refresh
> every 5 minutes (set this in Report Properties).
> >>>>>>>>>>
> 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
> >>>>>>>>>>>>>>>'
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
> "MustangDJB" <MustangDJB@.discussions.microsoft.com> wrote in message
> news:E12C4DCA-AF89-4770-9649-6E0775FA42ED@.microsoft.com...
> > Which specific post? There are so many, I'm not sure which one
> > applies...
> > "Vince Sefcik" wrote:
> >
> >> This was discussed in the forum several months ago. You can find the
> >> discussion by going to
> >> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx and do
> >> a
> >> search on the text "First Time Delay on Client Systems".
> >>
> >> "Andy Jones" <ajones@.rheemac.com> wrote in message
> >> news:eJAhsvihFHA.2424@.TK2MSFTNGP09.phx.gbl...
> >> > When a client types in the homepage of the RS it takes minutes to open
> >> > instead of seconds. It is running on a W2K3 machine with SQL 2000 and
> >> > the
> >> > clients are a mix of XP and 2K Pro. Any advice would be great. Oh this
> >> also
> >> > happens on the server itself.
> >> >
> >> > Once you open it once it opens in seconds from then on until you logoff
> >> and
> >> > back on to the pc again. Then it is slow again.
> >> >
> >> > Thanks!
> >> >
> >> >
> >>
> >>
> >>
>
>sql