Skip to content

How to improve performance for SharePoint and Project Server Part 1

March 15, 2014

Slow performance of SharePoint & Project Server

If you are one of those facing slow performance of SharePoint sites, try one or all of the items mentioned below. Tuning your SQL server will definitely help you to improve site performance.

I try to put all items at one place here and I will also try to post supporting links where ever possible.

These steps can be used in SharePoint 2010/2013 with or w/o project server running on SQL server 2005/2008 or 2012.

 1-      Antivirus software makes SharePoint/Project Server performance slow. Folder mentioned musts  be excluded if file level antivirus software is being used on the servers. See list of folders at:

2-      Wake up script can save user from facing site slowness when hitting the site for the first time after nightly application pool recycle (usually at 9am in the morning).

3-      Add SharePoint Cert in the Trusted Root certificate authority

If you are getting event ID 8421 in event viewer, this will also resolve that issue.

4-      I resolved a performance issues for one of my customer by setting  NIC Card configuration property named “Link Speed & Duplex”to 1000 Mbps, I don’t know why it was set to 100Mbps or how it got there but took me long to find this. You should check with your network admin also before making any changes to this property.

5-      Check with your network administrator for TCP Chimney Offload By Default in Wind 2008 Servers, this setting is “Automatic”, we need to disable it if it’s not. “netsh int tcp set global chimney=disabled

( Why :

6-      On your SQL server enable Common Language Runtime

sp_configure ‘clr enabled’, 1

 7-      For the project data bases  set AUTO_CLOSE property  to False

8-      For project server databases set  AUTO_UPDATE_STATISTICS and AUTO_UPDATE_STATISTICS_ASYNCHRONOUSLY properties to True

9-      Discuss data base maintenance plans with your DB Admin. In short index rebuilding is helpful to improve performance. Check &

10-   SQL server MAX Degree of parallelism should be set to 1, talk to your DBA if not sure about this property.

11-   Most of the time SharePoint server and SQL server are in the same subnet. But in case they are not, moving SharePoint server in the same subnet as DB server will improve performance as well.

12-   Check to see if you have enough RAM on server, check RAM, CPU usage on servers especially on SQL and all SharePoint servers.

13-   If you have Project Server installed on top of your SharePoint and facing slowness talk to your DB team and get a report on slow running queries. Try to enhance these queries so you can get the same result in less time if possible.

14-   If you have project server installed on top of SharePoint make sure you don’t go beyond the recommended number of custom fields. Impact can be significant  if you are using more than recommended custom fields at

15-   Now the last and my favorite, Add additional TempDB files. There is lots of information on it but only thing I will share from my experience is that you can create multiple files and this will definitely improve performance but don’t go crazy on creating additional TempDB files using some formula or with number of CPUs. Too many TempDB files can also be an impact on performance. Start with additional 2 or 3 files and test your application for any improvement first, you can add more TempDB based on Sever CPU and Drives availability.

Search for TempDB and read the section that has information about TempDB at

Some more information:

I will try to add more here on how you can tune your IIS but need to test few things before that.

Feel free to share more tricks, thoughts or any suggestions.

Hope this will help someone. Enjoy!

Please check out Part 2 for more information on improving performance.

  1. Bob permalink

    Great article. Did you ever get the IIS work completed?

  2. Thanks Bob,
    Did not get a chance to complete yet still on my list of ToDo items!

  3. Yuri permalink

    Can you give some specifics or a link concerning number 6? Enabling CLR is one of those things that DBAs like to have a good reason for.

  4. Enabling CLR is recommended if you are using Project sever specially, but I don’t see any harm if you enable for SharePoint as well. Project server send tons of queries to the databases and by enabling CLR on SQL server help execute queries in less time and reduce stress on Application servers. It also reduce the SQL round trips and improve performance. For more see enable CLR section at:

Trackbacks & Pingbacks

  1. Improve Performance for SharePoint and Project Server – Part 2 | SharePoint 2013

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: