SharePoint Server 2013 performance issue

Question

Hi,

We are maintaining SharePoint intranet site which was developed in SharePoint Server 2013 on premises, in our site architecture we have used 2 app servers, 2 wfe servers and 1 database server.

From few days on wards we are identifying our intranet site is loading slowly and especially search is very running very slow.

Please suggest in which area we need to focus to improve the site and search loading performance ?

---

Thanking You, Nagendra.

Answer 1

This might help you.

https://www.winwire.com/sharepoint-running-slow-heres-how-we-solved-the-mystery/

https://sharepoint.stackexchange.com/questions/65695/sharepoint-2013-extremely-slow

Please mark this as Answer if it help you.

Answer 2

first of all check CPU/memory utilization on WFE and DB servers when Sharepoint is slow (using Process explorer). What processes occupy most of resources?

---

Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - https://github.com/sadomovalex/camlex

Answer 3

Hi Nagendra, 

I agree with sadomovalex, first of all check CPU/memory utilization on WFE and DB servers when Sharepoint is slow. 

Besides, you can do following things to identify the issue.

Enable the developer dashboard and check where page is spending more time for loading.

http://www.sharepoint-journey.com/developer-dashboard-in-sharepoint-2013.html

Or IE Developer Tools can help you diagnose network-related issues by showing all the traffic that is related to a page and exposing details about individual connections. You can see the relative timing that each item on a webpage takes to load and render, so you can quickly see and solve problems.

http://msdn.microsoft.com/en-us/library/gg130952(v=VS.85).aspx

Best Regards, 

Lisa Chen 

---

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [e-mail].

SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

Answer 4

Hi Nagendra.

Did you make any change on the farm after which you've noticed this slowness?
First of all, you should check CPU, disk and memory usage on each of the servers in the farm; you can use the Windows Resource Monitor and Performance Monitor to asses those performance indicators.
What about the Search Service application? Could you share some information about its topology?

Bye.

---

Luigi Bruno
MCP, MOS, MTA, MCTS, MCSA, MCSE

Answer 5

Hi,

We have checked in WFE, App and DB servers CPU utilization and memory usage, Avg CPU utilization is 10 - 15% and memory usage is 20 - 30%.

In the central administration Monitoring we are getting one warning like "Some content databases are growing too large", there is any performance impact on site with this issue? 

---

Thanking You, Nagendra.

Answer 6

Hi,

We have checked in WFE, App and DB servers CPU utilization and memory usage, Avg CPU utilization is 10 - 15% and memory usage is 20 - 30%.

In the central administration Monitoring we are getting one warning like "Some content databases are growing too large", there is any performance impact on site with this issue? 

---

Thanking You, Nagendra.

Large (more than 100 GB) content databases are more likely to cause the application to stop responding when you perform operations that affect entire databases: you can refer to the document at https://docs.microsoft.com/en-us/sharepoint/technical-reference/some-content-databases-are-growing-too-large to know how to deal with such a warning?
What about the Search Service application? Could you share some information about its topology?

Bye.

---

Luigi Bruno
MCP, MOS, MTA, MCTS, MCSA, MCSE

Answer 7

Hi Luigi,

Please find the below our search topology.

Answer 8

what is the current sizes of content databases? MS recommends that content db size doesn't exceed 200Gb: Software boundaries and limits for SharePoint 2013/Content database limits. You may check size of content db on SQL server > SQL Management Studio.

---

Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - https://github.com/sadomovalex/camlex

Answer 9

Hi Luigi,

Please find the below our search topology.

The Search Service topology is redundant, maybe you could consider partitioning the index in two parts if there are many items in the index itself.
What about the medium size of each content database? Do they exceed the 200 GB recommended maximum size?

Bye.

---

Luigi Bruno
MCP, MOS, MTA, MCTS, MCSA, MCSE

Answer 10

Hi Sadomovalex,

Thank you for your reply!!!

Our production content database size is : 1548.2 GB, in this search service application crawl DB size is : 42 GB.

---

Thanking You, Nagendra.

Answer 11

so content db size is ~7x times greater than recommended by MS. This is most probably reason of performance problems. In this case you may split site collections across different databases:

1. create new content databases (New-SPContentDatabase)
2. optional: change recovery mode to Simple (see Problem with creating new content database for web application in Sharepoint and Full recovery mode)
3. move site collections to new content databases (Move-SPSite)
4. run Gradual site delete timer job - it will delete site from source content db
5. shrink source content db - it will reduce size of source content db

Your goal is to split content to content databases so size of each content db won't exceed recommended 200Gb.

---

Blog - http://sadomovalex.blogspot.com
Dynamic CAML queries via C# - https://github.com/sadomovalex/camlex

Answer 12

Hi Sadomovalex,

As per your suggestion we have created new content databases and moved site collections to new content database using Move-SPSite command, after that we ran Gradual site delete timer job as well.

In the final step shrink source content database, there is any powershell command to shrink database or we have only option to execute from sql server management studio ?

---

Thanking You, Nagendra.

Answer 13

Hi Sadomovalex,

As per your suggestion we have created new content databases and moved site collections to new content database using Move-SPSite command, after that we ran Gradual site delete timer job as well.

In the final step shrink source content database, there is any powershell command to shrink database or we have only option to execute from sql server management studio ?

---

Thanking You, Nagendra.

I'm not aware of any PowerShell cmdlet that is specifically aimed at shrinking SQL Server databases files.
You could take a look at the PowerShell script at https://www.powershellgallery.com/packages/dbatools/0.8.945/Content/functions%5CInvoke-DbaDatabaseShrink.ps1.

Bye.

---

Luigi Bruno
MCP, MOS, MTA, MCTS, MCSA, MCSE

Answer 14

Thank you Sadomovalex and Luigi Bruno

---

Thanking You, Nagendra.

Answer 15

Thank you Sadomovalex and Luigi Bruno

---

Thanking You, Nagendra.

You're welcome, Nagendra.

Bye.

---

Luigi Bruno
MCP, MOS, MTA, MCTS, MCSA, MCSE