Method and device for monitoring performance

Abstract

The invention provides a method and device for monitoring performance. According to the method and device for monitoring the performance, a monitoring script is compiled aiming at a function, when the function is called, the function is not directly called, and the monitoring script of the function is firstly called to start monitoring on the function; after the monitoring script is called, the function continues to be called, and monitoring on the function is achieved. Due to the fact that the function is used for describing the performance, it is equivalent that performance monitoring is achieved. By means of monitoring, the problem causing a performance bottleneck can be fast located, and efficiency is greatly improved.

Description

technical field [0001] The present application relates to computer technology, in particular to a performance monitoring method and device. Background technique [0002] In the process of large-scale program development, some performance bottlenecks are often encountered. For example, in the case of high concurrency, processing failures such as: the database connection pool is too low, the number of server connections exceeds the upper limit, and database lock control is insufficiently considered, etc.), Memory leaks, such as memory failure during long-term running, downtime, etc., CPU usage deviations, such as high CPU usage due to high concurrency, excessive log printing, etc. [0003] In order to ensure the smooth progress of program development, it is necessary to quickly locate the cause of performance bottlenecks in order to improve the efficiency of program development. Contents of the invention [0004] The present application provides a performance monitoring met...

AI Technical Summary

Problems solved by technology

[0002] In the process of large-scale program development, some performance bottlenecks are often encountered. For example, in the case of high concurrency, processing failures such as: the database connection pool is too low, the number of server connections exceeds the upper limit, and database lock control is insufficiently considered, etc.), Memory leaks, such as memory not being released normally during long-term running, downtime, etc., CPU usage deviations such as high CPU usage due to high concurrency, excessive log printing, etc.

Images