Performace tuning- URGENT

Hi,

Can anyone let me know how I can improve on the performance on loading the
WSS page.

I have two performance issues:

1. The page take a very long time to load for the first time. Also, if there
are no hits to the server and when the user tries to hit the server it again
takes a long time to load the page.

2. I have a â??Excluded pathâ?? , all the pages from this directory takes longer
time to load than the other pages. I have pages where I have a combination of
webparts (which loads fast) and asp.net pages (from the extended path) that
take a longer time to load.

Please let me know how I can resolves these two performance issues.

Thanks

Engelbert
Mon Aug 14 23:02:34 CDT 2006

On 1 - first part - only .

This is the result of loading the ActiveX components the browser needs. You
can avoid it by using a browser (Firefox for instance) that doesn't support
ActiveX as this will not download the components. The cost is that you lose
the functionality provided by Actove X.

Engelbert


"Dan" <Dan@discussions.microsoft.com> wrote in message
news:5E196979-E3A7-443C-9416-F03751DB70A8@microsoft.com...
> Hi,
>
> Can anyone let me know how I can improve on the performance on loading the
> WSS page.
>
> I have two performance issues:
>
> 1. The page take a very long time to load for the first time. Also, if
> there
> are no hits to the server and when the user tries to hit the server it
> again
> takes a long time to load the page.
>
> 2. I have a 'Excluded path' , all the pages from this directory takes
> longer
> time to load than the other pages. I have pages where I have a combination
> of
> webparts (which loads fast) and asp.net pages (from the extended path)
> that
> take a longer time to load.
>
> Please let me know how I can resolves these two performance issues.
>
> Thanks
>

Todd
Tue Aug 15 08:41:34 CDT 2006

Dan, another part of 1 could be the process spinning down on the server if
the page hasn't been hit in a while. If WSS hasn't been accessed in a while
IIS will unload it from RAM to help performance. The first person to hit
the site after that happens will have to wait for WSS to load back up before
they get their page. You can tweak this in IIS under the performance tab of
the Application Pool that WSS is running as. Uncheck the box next to "Idle
Timeout."

Likely Englebert's solution is the correct one though.

tk
"Engelbert" <Engelbert@discussions.nospam.com> wrote in message
news:OpzJ7%23BwGHA.4872@TK2MSFTNGP02.phx.gbl...
> On 1 - first part - only .
>
> This is the result of loading the ActiveX components the browser needs.
> You can avoid it by using a browser (Firefox for instance) that doesn't
> support ActiveX as this will not download the components. The cost is that
> you lose the functionality provided by Actove X.
>
> Engelbert
>
>
> "Dan" <Dan@discussions.microsoft.com> wrote in message
> news:5E196979-E3A7-443C-9416-F03751DB70A8@microsoft.com...
>> Hi,
>>
>> Can anyone let me know how I can improve on the performance on loading
>> the
>> WSS page.
>>
>> I have two performance issues:
>>
>> 1. The page take a very long time to load for the first time. Also, if
>> there
>> are no hits to the server and when the user tries to hit the server it
>> again
>> takes a long time to load the page.
>>
>> 2. I have a 'Excluded path' , all the pages from this directory takes
>> longer
>> time to load than the other pages. I have pages where I have a
>> combination of
>> webparts (which loads fast) and asp.net pages (from the extended path)
>> that
>> take a longer time to load.
>>
>> Please let me know how I can resolves these two performance issues.
>>
>> Thanks
>>
>
>

Dan
Tue Aug 15 08:53:01 CDT 2006

Todd & Englebert,

Thank you for your inputs. They were of great help to me.
Can you also try and help me with the 'Excluded path' issue, if happen to
find solution.
Thanks in advance
Dan

"Todd Klindt [MVP]" wrote:

> Dan, another part of 1 could be the process spinning down on the server if
> the page hasn't been hit in a while. If WSS hasn't been accessed in a while
> IIS will unload it from RAM to help performance. The first person to hit
> the site after that happens will have to wait for WSS to load back up before
> they get their page. You can tweak this in IIS under the performance tab of
> the Application Pool that WSS is running as. Uncheck the box next to "Idle
> Timeout."
>
> Likely Englebert's solution is the correct one though.
>
> tk
> "Engelbert" <Engelbert@discussions.nospam.com> wrote in message
> news:OpzJ7%23BwGHA.4872@TK2MSFTNGP02.phx.gbl...
> > On 1 - first part - only .
> >
> > This is the result of loading the ActiveX components the browser needs.
> > You can avoid it by using a browser (Firefox for instance) that doesn't
> > support ActiveX as this will not download the components. The cost is that
> > you lose the functionality provided by Actove X.
> >
> > Engelbert
> >
> >
> > "Dan" <Dan@discussions.microsoft.com> wrote in message
> > news:5E196979-E3A7-443C-9416-F03751DB70A8@microsoft.com...
> >> Hi,
> >>
> >> Can anyone let me know how I can improve on the performance on loading
> >> the
> >> WSS page.
> >>
> >> I have two performance issues:
> >>
> >> 1. The page take a very long time to load for the first time. Also, if
> >> there
> >> are no hits to the server and when the user tries to hit the server it
> >> again
> >> takes a long time to load the page.
> >>
> >> 2. I have a 'Excluded path' , all the pages from this directory takes
> >> longer
> >> time to load than the other pages. I have pages where I have a
> >> combination of
> >> webparts (which loads fast) and asp.net pages (from the extended path)
> >> that
> >> take a longer time to load.
> >>
> >> Please let me know how I can resolves these two performance issues.
> >>
> >> Thanks
> >>
> >
> >
>
>
>