Monitor SharePoint Efficiency (vi) – Optimize content storage and access

After you've removed all the problems in your SharePoint environment with the tools you mentioned earlier, there are two ways to get your SharePoint system to respond quickly.

One is to increase the number of servers, using better hardware, this will undoubtedly be a high cost. Another way is to optimize the existing structure to make full use of the already existing hardware.

SharePoint systems In some typical cases, there is no need for additional optimizations to be able to have a good response speed. For example, users upload a common office/pdf file, the site is for the internal use of the intranet, the number of users is not particularly large.

But what if it's a specific situation?

For example, users upload a lot of big video files? This will definitely take up a lot of SQL storage space and slow SharePoint. This requires optimizing SQL storage and moving the binary data outside the SQL database. This will use RBS technology.

For an introduction to RBS, please refer to

Overviewof RBS

Remote Blobstore Provider Library Implementation specification

For example, the site is facing the public Web site? The number of visitors may be numerous. But most people come to see that only a few can edit it. This allows the cache to be turned on, allowing the page to load faster.

For caching, please refer to:

Caching in SharePoint

In addition to this, there are some database techniques that can improve the speed of SharePoint.

1. database files (. MDF) and log files (. LDF) to a different disk. Because when we write to SharePoint, SQL Server needs to modify both the database file and the log file. If the two files are on the same disk, then the disk needs to process two files. and stored separately, you can process one file per disk.

At the same time, this is useful for data recovery. If you put it on the same disk, the database files and log files are lost once the disk is damaged.

2. If you have sufficient resources, you can use a RAID array to store the database and log files. It is best to put the database file into RAID5, and put the log file to RAID10.

It is important to note that prior to any optimization, the test environment needs to be tested before it can be implemented into a production environment. Moreover, even if an optimization makes the speed up, it does not mean that it is worthwhile to implement into the production environment, such as the response time from 3 seconds to 2.7 seconds, not for the user to be aware of.

Monitor SharePoint Efficiency (vi) – Optimize content storage and access