Sunday, August 4, 2013

Improve SharePoint Performance by limiting memory allocation of SQL Server

Many times I have seen developers complaining about their SharePoint development environment performance. Since they have SharePoint standalone installation on their development Virtual Machine they always complain their machine is too slow.

This is not only the case with development environment, even for SharePoint Test, Staging and Production environment, we always blame SharePoint the cause of performance hit. But wait a min the problem is not with SharePoint there could be other factors which might be causing performance issue. And one of the factor is default settings of SQL Server database. In this article I am not going to touch all other factors but yes I am going to touch base very important and quick setting which you can do to boost your SharePoint environment performance.

SQL Server is the one who eats all your memory every time, because by default it is given freedom to SQL Server to consume all memory on the server. By Default, SQL Server is set to use max 2TB of RAM. You might not be having 2 TB RAM in your environment, you might have 8 GB, 16 GB, 32 GB or more depending upon your farm and size of SharePoint installation. So what will happen if SQL Server itself is free to take up to 2 TB RAM, then whenever any operation comes to SQL Server it will try to consume as much as it can consume. What will happen to the OS and other processes you have running on the server, they also need some memory, they are also responsible for doing their task. So here is what you can do to limit the memory size of SQL Server and tell him that you are not the one there are others who also needs some memory. At the end you need to make sure your SQL Server and your Server they are not competing themselves to the same memory resource this causes bad performance on the server.

No comments:

Post a Comment