Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

WSS Performance and How to Improve it

  Asked By: Lukas    Date: Nov 03    Category: Sharepoint    Views: 718

We recently installed WSS and are about ready to start developing our portal
on it. However, we noticed that the initial home page (or any page in the
site) takes a long time to load.

Are there any performance tips and tricks that we can apply to speed up the
loading of the first page in the site. This slow load is not acceptable to
our users.

Share: 

 

11 Answers Found

 
Answer #1    Answered By: Ted Gilmore     Answered On: Nov 03

here could be any number of factors that relate to why the page
doesn't load  quickly:

1. Server is busy processing other threads
2. Router is saturated
3. Workstation is under-powered
4. Server is busy processing lots 'o hits on the portal
5. Others????

You should do some performance  monitoring of your servers to figure out
where the bottleneck is. SPS03 is a resource hungry program and needs
lots of RAM and processing power.

 
Answer #2    Answered By: Monte Cooley     Answered On: Nov 03

There’s always loading the app pool … and the standard load  up the site  for the first time  delay.

 
Answer #3    Answered By: Guadalupe Bullock     Answered On: Nov 03

yeah this is usually the initial  load and would happen again if it was idle for
a period of time.. if the box is still slow, check the amount of ram in use and
possibly increase it - for about 1000 users  i have 2gb in each front end. from
what i can tell.. it looks like ASP.net likes to live in memory/pagefile. isnt
that right developers?

and if it is "always" slow  and you have a suitable amount of memory, the cpu
would be the last place to look. i have a dev box tho that runs a 1ghz with 2gb
memory and its peppy enough.

 
Answer #4    Answered By: Nathanial Mcclure     Answered On: Nov 03

I'm having the same issue at the moment, but I'm hoping it's because I'm running WSS in a test environment on a P2 350 Server with 786MB of ram. When I'm at a remote site  it takes  about 45 seconds for the first page  to load. At my main site it takes about 5 seconds. Furthermore, at my remote sites, I'm going over a 128K WAN link which is slow  already.

In the next couple weeks, I'm going to be going live with WSS to replace my exisiting Intranet product, but it will be loaded on a Dual P4 server with 8GIG RAM. I'm also upping the WAN speeds to 384K. I'm hoping with these upgrades and faster servers the load  times will be minimal for everyone.

 
Answer #5    Answered By: Matt Prince     Answered On: Nov 03

After I installed  WSS, I observed that the first page  loaded up very
slowly. I was trying to open the page on the same server.
However, when I go to my machine and access the first page, it loads up
pretty fast. Not coincidental.
Whenever a page would not come up on the server, I quickly go to my
machine and access the page instantly.
Server: Win2k3; Office 2003; WSS 2
My Machine: Win2000; Office 2000
I was wondering if someone other than me observed this to be True.
I still would like to hear more about performance  tuning with WSS in
this forum. Thanks,

 
Answer #6    Answered By: Brooks Bond     Answered On: Nov 03

Have you read the white papers on performance  tuning and capacity
planning for WSS? Please read those first before asking general
questions about that topic here.

 
Answer #7    Answered By: Gregg Wilkinson     Answered On: Nov 03

And probably 10 other things that we could mention if we took the time  to list them out……….

 
Answer #8    Answered By: Darrel Sexton     Answered On: Nov 03
 
Answer #9    Answered By: Tory Sellers     Answered On: Nov 03

In order to understand why the platform is running slow, it is important that we know the layout of the server(s). Are you using a Farm? How many front-end servers are your using? Is your Index and SQL Server(s) on separate server platforms? Are you using a switch between front-end servers (such as Alteon)? As stated before, so many factors can effect performance. Look at your Server configurations (hard drive, ram, processor speed, etc) and see if you are overtaxing the system. Are you using and special SharePoint configurations (and custom apps or configuration)? Was it working fine then just started slowing down? Was anything significant occur around that time?

 
Answer #10    Answered By: Agustin Miranda     Answered On: Nov 03

This is very common in any .NET application. The first request for any
resource takes  longer than subsequent requests for it. This has to do
with the way that the ASPX pages are JIT compiled.

From my observation you will likely wait at these times:

1. The first time  any page  is requested from the site.
2. The first time the Settings link is clicked.
3. The first time a property builder is requested.
4. If you're disconnected from the Internet, you request the Add Web
Parts tool pane and you haven't disabled the online gallery
(recommended).

There are probably other times but these are the most noticeable.

 
Answer #11    Answered By: Arron Middleton     Answered On: Nov 03

This is very common in any .NET application. The first request for any
resource takes  longer than subsequent requests for it. This has to do
with the way that the ASPX pages are JIT compiled.

From my observation you will likely wait at these times:

1. The first time  any page  is requested from the site.
2. The first time the Settings link is clicked.
3. The first time a property builder is requested.
4. If you're disconnected from the Internet, you request the Add Web
Parts tool pane and you haven't disabled the online gallery
(recommended).

There are probably other times but these are the most noticeable.

 
Didn't find what you were looking for? Find more on WSS Performance and How to Improve it Or get search suggestion and latest updates.




Tagged: