Office OA system performance analysis case

foreword

The teacher in the information center reported that the user reported that the office system was slow to access, and it was necessary to understand the operation of the system through the traffic analysis system. This report specifically analyzes the performance data of the system.

The information center has deployed the NetInside traffic analysis system, using the traffic analysis system to provide real-time and historical raw traffic for security forensics, application transaction analysis, network quality monitoring and deep network analysis.

Content of report

The content of this report mainly includes: comprehensive system analysis, performance analysis of the first slow page, performance analysis of the second slow page, and error analysis of the office system page.

analysis time

The report analysis time range is: 2022-03-22 11:00-03-22 14:00, with a total duration of 3 hours.

Analysis conclusion

1. During the period from 11:00 to 14:00 on March 22, the office system had 174,267 visits.

2. Among them, 0.14% of the visits are slow visits, that is, there are 251 visits with a duration of more than 5 seconds.

3. One of the slow accesses, the client 211.82.101.245, the access time is 60 seconds, the main reason is that the server response time is too long.

4. The second slow access, client 221.XXX.XXX.227, the access time is 5 seconds, the main reason is that the server takes a long time to respond.

5. Analyzed that there were 402 HTTP 400 page errors, one of which was a page error, and the client was 223.104.39.100. The reason was that the HTTP 404 response error meant that the user entered a wrong connection, and the returned page did not exist or had been deleted.

Detailed analysis

System Comprehensive Analysis

From 11:00 to 14:00 in the office system, there were 251 slow accesses and 402 HTTP 400 errors.

From 11:00 to 14:00 on March 22, the total number of visits was 174,267.

Among them, 251 visits lasted more than 5 seconds. The figure below shows the distribution trend of slow visits.

The first slow page performance analysis

Sort according to the slow access pages, and view the system slow access information.

Slow access to the first slow page family is shown in detail. When accessing these objects, the page delay is relatively large, and the maximum response time is 60 seconds.

In-depth analysis of the first slow access, the client is 211.XXX.XXX.245. The distribution of 60 seconds is shown in detail due to high server response times.

The second slow page performance analysis

Slow access to the second slow page family is shown in detail.

In-depth analysis of the first slow access, the client is 221.XXX.XXX.227. The distribution of 5 seconds is shown in detail due to long server response times.

When accessing the object circled in the figure, the access time reached 5 seconds.

Error analysis of office system page

From 11:00 to 14:00 on March 22, a total of 402 HTTP 400 response codes were generated.

According to the analysis, when accessing these page clusters, an HTTP 400 error occurred. Among them, the most visited page family generated 319 page errors.

Analyze one error report in the page cluster.

Detailed analysis of error results.

suggestion

Through the analysis of the performance data of the office system, it was found that the reason for the slowness was the long response time of the server, which was a software problem and had nothing to do with the network.

Through the analysis of the page error report of the office system, it was found that when some teachers accessed the system, the page was not found, which was a software problem.

It is recommended to contact the software developer, explaining that some teachers access the office system very slowly, and when accessing the system, there is a phenomenon that the page is not found. After analysis, it is found that it is a software problem. Ask them to optimize their technology and support it. If you need more details information, we will cooperate to provide.

Guess you like

Origin blog.csdn.net/NetInside_/article/details/130930799