Monitor SharePoint Efficiency (iv) – Conduct efficiency tests

Before you actually go online, you need to do a good job of testing the efficiency to avoid slow response and impact on the user experience. So what should be done before the production environment on-line to do efficiency testing?

It is necessary to simulate a test environment similar to the production environment to accomplish this task. When building a test environment, it is important to be aware that the test environment is close enough to the production environment. Like what:

• Same hardware specifications as the production environment
• The same software settings
• The same operating system version
• The same third-party solution
• Same user, user group and permission settings

In addition, it is also possible to simulate the potential future storage capacity of the production environment. For example, if you expect to have 1TB of data in your production environment three years from now, you need to simulate this data in a test environment.

Once the environment is ready, tools are also needed to simulate concurrent access-load testing. You can use Microsoft's official SharePoint Load Test Kit in conjunction with Visual Studio to do simulation testing, and if the production environment is expected to be accessed by 1000 people at the same time, simulate 1000 people with Visual Studio, Look at the response time for SharePoint within acceptable. (For more detailed information, please refer to here)

When doing a load test, the following metrics are monitored:

1. What is the use of memory and Cpu,io on each server while accessing the same page, or the same file, or the same video?

2. When uploading files at the same time, what is the usage status of memory and Cpu,io on each server?

3. How long does it take to do a full crawl?

4. While crawling, the impact does not affect the corresponding time?

5. How long does it take to make a full backup? Does it affect response time?

After testing, the system of the production environment can be launched.

The system should still be routinely monitored for efficiency, because as users increase, content increases, third-party solutions are deployed, SharePoint features are activated, and so on, the system's efficiency is likely to decline.

Monitor SharePoint Efficiency (iv) – Conduct efficiency tests