A Case Study of Library Flow Monitoring Performance Analysis

foreword

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

The library 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 main contents of this report are: comprehensive system analysis, slow page performance analysis, and page error analysis.

analysis time

The report analysis time range is from 9:00 on March 30th to 14:00 on March 30th, with a total duration of 5 hours.

Analysis conclusion

1. During the period from 9:00 to 14:00 on March 30, the library system had 634 visits.

2. Among them, 0.7% of the visits are slow visits, that is, there are 6 visits longer than 5 seconds in the analysis.

3. One of the slow visits, the client 222.249.253.5, took 7 seconds to visit. The main reason is that there are too many contents in the visited page.

4. Analyzed that there were 250 HTTP 400 page errors, one of which was a page error, and the client was 222.249.253.5. 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.

5. Through the analysis of the reasons for the slowness of the library system, it is found that the network delay is not large, and the server response time is also fast, but some teachers feel that the slowness is due to too much content in the webpage, and one of them reached 118 responses.

Detailed analysis

System Comprehensive Analysis

From 9:00 to 14:00, the system generated 6 slow accesses and 250 HTTP 400 errors.

From 9:00 to 14:00, a total of 634 visits were made.

Among them, 6 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.

The slow access to the first slow page family is displayed in detail. When accessing this object, the page time is 7 seconds, showing that the server time and network time are not large, and the number of responses is 118.

You can also view the specific details by expanding this visit. When accessing this object, this object contains 118 response objects.

System page error analysis

From 9:00 to 14:00, a total of 250 HTTP 400 response codes were generated.

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

Analyze one error report in the page cluster.

Detailed analysis of error results.

suggestion

The main reason affecting the speed of the library system users is not the server response problem, nor is it caused by the large network delay, but the system has too much content on a single page, resulting in a long transmission time. Therefore, it is caused by insufficient system development and optimization. If you want to solve this problem, it is recommended to contact the developer to optimize the page (for example, reduce 118 access transfer objects to about 20), which can greatly speed up page access.

Guess you like

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