Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Performance Issues

  Asked By: Gino    Date: Jun 13    Category: MOSS    Views: 808

Anyone got a good reference to performance tips for MOSS?

One of my MOSS boxes is intermittently slow, but the performance
indicators are not showing me a clear reason as to why response time for
loading pages is so poor.

(Literally intermittent... one page will load super fast, 5 minutes
later another will load super slow... max users are about 75 on this
box.)

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Richard Davis     Answered On: Jun 13

I wonder if the app pool (or IIS as a whole) is recycling often; is it
possible that some third-party or custom code is leaking memory?

Also, how is MOSS configured on this box? Is it a single-server
installation (database and everything)? If there's a decent amount of
traffic, you could end up with resource conflicts.

 
Answer #2    Answered By: Mason Davis     Answered On: Jun 13

Check app pool recycling, good  idea. Also check your SQL I/O. That's
usually the biggest performance  problem I see from day to day.

 
Answer #3    Answered By: Savannah Pena     Answered On: Jun 13

Is there a simple way to check SQL I/O, or it is a SQL DBA thing? I wonder as a
sharepoint engineer ,how to identify it is a SQL issue before dispatching the
problem

 
Answer #4    Answered By: Upendra Bordoloi     Answered On: Jun 13

I would recommend using MOM or System Center. Of course, with budget
constraints you would have to identify all of the counters and
thresholds to establish a baseline. I did post a list of those
counters to as a response  to your original question.

 
Answer #5    Answered By: Ali Javed     Answered On: Jun 13

We had a client with serious intermittent  MOSS problems... Couldn't
really find an issue.

90% was solved when we added 1GB of extra RAM... So memory is indeed
something to check (leaks?). In our case it was just that the site was
heavily loaded (over 6K user for 2 poor WFEs with 2GB RAM !).

 
Answer #6    Answered By: Karrie Wooten     Answered On: Jun 13

Here are a list of counters that are, traditionally, used by most
Enterprise IT departments to monitor an enterprise-wide SharePoint
infrastructures. Of course, there a number of varibles that
contribute to, either, a decrease or increase in server performance.
I am going to make a number of assumptions here due to lack of
knowledge of your SharePoint deployment.

Server Role Counter Category
All servers Memory\Available Mbytes Memory*
Memory\% Committed Bytes in Use Memory*
Memory\Pages/second Memory
System\Processor Queue Length Processor
Processor\% Processor time  Processor*
Network\Network Queue Length Network

Web front-end server
Process (w3wp)\% Processor Time Processor*
Process (w3wp)\Private Bytes Processor*
Web Service\Connection Attempts/second Application load*
ASP.NET\Worker Process Restarts Application load
Web Service\Current Connections Application load*
Web Service\Bytes Sent/Sec all instances)Network
Web Service\Bytes Received/Sec (all instances)Network
.NET CLR Data\SQL Client: Pooled and NonPooled
Connections (instance _global_) Application load
.NET CLR Data\SQL Client: Failed Pooled Connections(instance _global_)
Application load


Back-end database server
Process (sqlserver)\% Processor Time Processor*
Process (sqlserver)\Private Bytes Memory*
SQL Server\SQL Server: General Statistics: Current Connections
Database*
SQL Server\SQL Server: General Statistics: Logins/Sec
Database*

The counters with and "*" are used to establish a baseline over time.

Honestly, I would encourage you to leverage System Center or MOM to
monitor your SharePoint deployment to increase the overall
performance of each role in the farm.

 
Didn't find what you were looking for? Find more on Performance Issues Or get search suggestion and latest updates.




Tagged: