Who's Online
5 visitors online now
0 guests, 5 bots, 0 members
Support my Sponsor
  • An error has occurred, which probably means the feed is down. Try again later.

Common troubleshooting step : SharePoint 2013, SharePoint 2010 and SharePoint 2007 Performance issue \ Web Site slow

SharePoint 2013, SharePoint 2010 and SharePoint 2007 Performance issue \ Web Site slow

I saw that this is a very commonly faced issue specially with SharePoint 2013. Below are few pointer which can help you resolve the issue.

Lets start with Questions.

  1. Is it a HTTP or HTTPS site. Normally if it is HTTPS site we need to install SSL certificate on below 3 locations:
  • IIS manager > Select server > Certificate on right hand side
  • SharePoint Central Admin > Security > Trusted Root certificate > Import > Select certificate > OK
  • We need to make sure we import intermediate Certificates in Central Admin(You will get the intermediate Certificates from Certificate provider)
  • Most important we need to install certificate on SharePoint servers Certificates console. To do so Click on Start > Run > Type  MMC > File  > Add\remove snap-in > Certificates > Add> OK > Local Machine > Expand folder > Trusted Root certificate > Right click certificates folder > All tasks > Import > Next > Select File > Next >Finish.
  • Now we also need to make sure we import the Intermediate Certificates. In the Certificates console Intermediate certification Authorities > Right click certificates folder > All tasks > Import > Next > Select the intermediate Certificates. > Next >Finish (You will get the intermediate Certificates from Certificate provider)
  1. Do we have high CPU Or memory use on server. Use sharepoint PAL tool

http://pal.codeplex.com/discussions/474705

  1. How many servers in farm. Check each server one by one using host entry

Start > Run > Type “Drivers” > open ETC folder > open HOSTS file > Edit the hosts in notepad > add IP to URL  > try to browse site on each server  and check if any specific server causing performance issue

  1. What do we see error 404 in Fiddler traces. If we have any 404  error we need to make sure it is resolved

  2. Search indexing, if it kicks in, consumes resources that you might need on your WFEs and SQL servers for processing the migration of files

  3. Anti-virus software, if it is scanning every document that is uploaded, or is scanning the database or BLOB store directly, can slow things down tremendously

  • BLOB storage can affect performance—for better or worse.
  • Database growth sizing
  • Storage performance, of course, can affect the upload.
  • The bottleneck might be the connection between the WFE and SQL Server. Use a dedicated high-speed (Gig-E or 10Gig-E) network between WFE and SQL servers. Use teaming if NICs support it.
  1. The Distributed Cache Service in my farm is down, I removed the service from all systems in the farm. the command is :

Stop-SPDistributedCacheServiceInstance -Graceful
Remove-SPDistributedCacheServiceInstance

  1. Check if job-application-server-admin-service is causing Performance issue on server
  • Check the ULS + Eventviewer logs at the time when this issue happens.
  • Collect perflog files and execute PAL on that this will give you the complete analysis of processes and performance at that time.
  1. Use Developer Dashboard
  • Activate the Developer Dashboard from Powershell

$d = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings
$d.DisplayLevel = ‘OnDemand’
$d.TraceEnabled = $true
$d.Update()

  • Click on the icon to open the Developer Dashboard
  • Refresh the page
  • Click the page URL in the dashboard

Comments are closed.