MOSS Performance issues
We are facing some of the performance issues on our farm.
Following are the farm details
· MOSS 2007
· 4 GB RAM on each server
· IIS 6.0
· Windows 2003 Standard Server SP2
· Two WFE servers load balanced
· Two ISA servers also load balanced.
· One Shared Services Provider also got central administration on.
· Two SQL servers clustered, one of them is active.
· 40 web Apps, all of them are extended.
When a group of 30 – 40 people trying to access the same site at the same time through internal network, it comes up with severe performance issues i-e site took long time to load or some of the users receive internal server error.
Any body could help me please that how we can solve the issue?
- ИзмененоMike Walsh MVPMVP, Модератор1 июля 2009 г. 14:46....... removed from Title - attention grabbing attempt
Ответы
- Hello DavUk,
first some questions...
* 32Bit or 64 Bit SQl and SharePoint Servers? (Hope you are not on 32 Bit :-))
* network bandwith allready checked?
I have faced a same issue when we head a 32Bit environment. What i used to find the root cause was to use PAL (http://www.codeplex.com/PAL) and monitored with perfmon the hole servers. In PAL is a MOSS 2007 template which has everything configured and it will show you in nice visuall way where your server get stressed.
the best... Its free :-)
Greetings,
Andreas- Помечено в качестве ответаLambert QinMSFT, Модератор9 июля 2009 г. 6:31
- Do you follow Best pratices, for tunning?Tune Web server performance
Create schedule jobs for Database, like "check database integrity, reoganize index, rebuild index, update statics, clean up history"....How to defragment Windows SharePoint Services 3.0 databases and SharePoint Server 2007 databasesHope this help.
André Lage Microsoft SharePoint and CRM Consultant
Blog:http://aaclage.blogspot.com
Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/- Помечено в качестве ответаLambert QinMSFT, Модератор9 июля 2009 г. 6:31
The 32 versus 64 bit question is critical. You are really going to struggle if you are running 32 bit and have more than a few web apps.
If it is 64-bit, then I would ask how you have the web apps mapped to application pools. How many app pools supporting those apps?
Next I would look at what the actual memory allocation is. Is it typically using 90% or more of the RAM? Is there RAM available or is everything currently cached?
If it is just a RAM issue you may be able to spread the load out to another WFE. If you are 32-bit though this isn't likely going to help since you have other core architectural issues.
Another thing to consider is your indexing schedule. The Indexer is on a seperate server, but it has to hit a WFE. If it is hitting one of the two you mentioned it will generate a pretty big load while indexing. If you have frequent indexes, many suggest setting up a WFE that is not behind the load balancer for indexing. Think of it like a utility server.
SharePoint Developer | Administrator | Evangelist -- Twitter -- Blog - http://nextconnect.blogspot.com- Помечено в качестве ответаLambert QinMSFT, Модератор9 июля 2009 г. 6:31
Все ответы
- Hello DavUk,
first some questions...
* 32Bit or 64 Bit SQl and SharePoint Servers? (Hope you are not on 32 Bit :-))
* network bandwith allready checked?
I have faced a same issue when we head a 32Bit environment. What i used to find the root cause was to use PAL (http://www.codeplex.com/PAL) and monitored with perfmon the hole servers. In PAL is a MOSS 2007 template which has everything configured and it will show you in nice visuall way where your server get stressed.
the best... Its free :-)
Greetings,
Andreas- Помечено в качестве ответаLambert QinMSFT, Модератор9 июля 2009 г. 6:31
- Do you follow Best pratices, for tunning?Tune Web server performance
Create schedule jobs for Database, like "check database integrity, reoganize index, rebuild index, update statics, clean up history"....How to defragment Windows SharePoint Services 3.0 databases and SharePoint Server 2007 databasesHope this help.
André Lage Microsoft SharePoint and CRM Consultant
Blog:http://aaclage.blogspot.com
Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/- Помечено в качестве ответаLambert QinMSFT, Модератор9 июля 2009 г. 6:31
- Hello,
I would also take a look and see if there is an accumulation of closed Web parts that weren't deleted. Add "?contents=1" to the end of your site's URL and see if this may be the case. Having a large number of closed Web parts, especially ones that are running queries, can bog down your performance.
Chris Caravajal MCTS SharePoint Help The 32 versus 64 bit question is critical. You are really going to struggle if you are running 32 bit and have more than a few web apps.
If it is 64-bit, then I would ask how you have the web apps mapped to application pools. How many app pools supporting those apps?
Next I would look at what the actual memory allocation is. Is it typically using 90% or more of the RAM? Is there RAM available or is everything currently cached?
If it is just a RAM issue you may be able to spread the load out to another WFE. If you are 32-bit though this isn't likely going to help since you have other core architectural issues.
Another thing to consider is your indexing schedule. The Indexer is on a seperate server, but it has to hit a WFE. If it is hitting one of the two you mentioned it will generate a pretty big load while indexing. If you have frequent indexes, many suggest setting up a WFE that is not behind the load balancer for indexing. Think of it like a utility server.
SharePoint Developer | Administrator | Evangelist -- Twitter -- Blog - http://nextconnect.blogspot.com- Помечено в качестве ответаLambert QinMSFT, Модератор9 июля 2009 г. 6:31
