CN115695227A - Performance testing method, device, electronic equipment and readable storage medium - Google Patents

Abstract

The application relates to the technical field of equipment performance test, and discloses a performance test method, a performance test device, electronic equipment and a readable storage medium, wherein the performance test method comprises the following steps: acquiring a log file; the log file comprises log data of the load balancing equipment during operation; analyzing the log file to obtain key information related to the user request; sending a test request to the load balancing equipment based on the key information; and determining the performance of the load balancing equipment based on the running state of the load balancing equipment when the load balancing equipment processes the test request. The performance test method provided by the application can simulate the online flow to complete the performance test of the load balancing equipment by analyzing the log file of the load balancing equipment, is favorable for improving the test accuracy, reduces the test cost and improves the test efficiency.

Description

Performance testing method, device, electronic equipment and readable storage medium

technical field

The present application relates to the technical field of equipment performance testing, and in particular, the present application relates to a performance testing method, device, electronic equipment and readable storage medium.

Background technique

With the continuous development of engineering technology, more and more application systems based on server clusters provide services for people's daily life and work. In the application system, a load balancing device, that is, a network service device, can be used to distribute traffic to multiple back-end servers and improve the external service capability of the application system. Among them, performing a performance test on the load balancing device to know the processing performance of the device is beneficial to ensure the stability of the application system.

In related technologies, when testing the performance of load balancing devices, offline testing methods are usually used. However, there are differences between the offline test environment and the online operating environment where the load balancing device is actually applied, resulting in low accuracy of test results. , and the test efficiency is low.

Contents of the invention

The purpose of the application aims to at least solve one of the above-mentioned technical defects, and proposes the following technical solutions:

In the first aspect, a performance testing method is provided, including:

Obtain a log file; the log file includes log data when the load balancing device is running;

Analyzing the log file to obtain key information related to the user request;

sending a test request to the load balancing device based on the key information;

Based on the running status of the load balancing device when processing the test request, the performance of the load balancing device is determined.

With reference to the first aspect, in the first implementation manner of the first aspect, the parsing of the log file obtains key information related to the user request, including:

For each of the log files, obtain the log information corresponding to the log attribute in the preset log template;

Each of the log information is screened to obtain key information related to the user request.

With reference to the first implementation manner of the first aspect, in the second implementation manner of the first aspect, before the filtering of each log information to obtain key information related to user requests, further includes:

Checking the validity of the log information in the log file;

Log files that fail the described legality checks are deleted.

With reference to the second implementation manner of the first aspect, in the third implementation manner of the first aspect, the checking of the validity of the log information in the log file includes:

Check the validity of the log information in the log file based on the preset exception label;

If it is determined that the log information in the log file carries information corresponding to the preset abnormal label, then it is determined that the log file has not passed the legality check;

If it is determined that the log information in the log file does not carry information corresponding to the preset exception tag, it is determined that the log file passes the validity check.

With reference to the second or third implementation manner of the first aspect, in the fourth implementation manner of the first aspect, the checking of the validity of the log information in the log file includes:

It is estimated that the log information in the log file includes an abnormal probability of abnormal information; the abnormal information includes: at least one of preset keywords, variable abnormal information, and distribution abnormal information;

If the abnormal probability is greater than the preset probability, it is determined that the log file has not passed the legality check;

If the abnormal probability is less than or equal to the preset probability, it is determined that the log file passes the legality check.

With reference to the first aspect, in a fifth implementation manner of the first aspect, the sending a test request to the load balancing device based on the key information includes:

Generate a file transfer curl command based on the key information corresponding to each log file through the preset request construction tool;

Sending a test request to the load balancing device based on the curl command.

With reference to the first aspect, in the sixth implementation manner of the first aspect, the determining the performance of the load balancing device based on the running status of the load balancing device when processing the test request includes:

After the load balancing device processes the test requests corresponding to each log file, obtain the running status information of the load balancing device;

determining an operating state of the load balancing device when processing the test request based on the operating state information;

If the operating state of the load balancing device is abnormal, it is determined that the performance is not up to standard;

If the running state of the load balancing device is normal, it is determined that the performance is up to standard.

With reference to the sixth implementation manner of the first aspect, in the seventh implementation manner of the first aspect, the running state information includes at least one of a state file and a core dump file; the state file is used to record all The information when the operating state of the load balancing device is normal; the kernel dump file is used to record the information when the operating state of the load balancing device is abnormal;

The determining the running state of the load balancing device when processing the test request based on the running state information includes:

Determine the operating state of the load balancing device when processing the test request based on whether the operating state information includes a core dump file; if the operating state information does not include a core dump file, determine the operating state of the load balancing device is normal; if the running state information includes a kernel dump file, determine that the running state of the load balancing device is abnormal;

And/or, based on the ratio of the number of files in the status file to the number of requests for the test request, determine the operating status of the load balancing device when processing the test request; if the ratio is greater than or equal to a preset ratio , determining that the operating state of the load balancing device is normal; if the ratio is less than a preset ratio, determining that the operating state of the load balancing device is abnormal;

And/or, based on the respective weight coefficients corresponding to the state file and the core dump file and the proportion of the number of files in the running state information, determine the corresponding standard value of the load balancing device when processing the test request ; If the standard attainment value is less than the preset standard attainment threshold, determine that the load balancing device is running abnormally; if the standard attainment value is greater than or equal to the preset standard attainment threshold, determine that the load balancing device is running normally.

In a second aspect, a performance testing device is provided, including:

The log obtaining module is used to obtain log files; the log files include log data when the load balancing device is running;

A log parsing module, configured to parse the log file to obtain key information related to the user request;

A request sending module, configured to send a test request to the load balancing device based on the key information;

A performance determining module, configured to determine the performance of the load balancing device based on the running state of the load balancing device when processing the test request.

The third aspect provides an electronic device, including a memory, a processor, and a computer program stored in the memory and operable on the processor. When the processor executes the program, the performance testing method shown in the first aspect of the present application is implemented.

In a fourth aspect, a computer-readable storage medium is provided. A computer program is stored on the computer-readable storage medium. When the program is executed by a processor, the performance testing method shown in the first aspect of the present application is implemented.

The beneficial effects brought by the technical solution provided by the application are:

After obtaining the log file, the application parses the log file and obtains the key information related to the user request, then sends a test request to the load balancing device based on the key information, and then determines the test request based on the running status of the load balancing device when processing the test request. The performance of the load balancing device; wherein, the log file includes the log data when the load balancing device is running, that is, the application can simulate online traffic by parsing the log file of the load balancing device to complete the offline performance test of the load balancing device. Effectively reduce the difference between the offline test environment and the online operating environment where the load balancing device is actually applied, improve the accuracy of offline test results, reduce test costs and improve test efficiency.

Additional aspects and advantages of the application will be set forth in part in the description which follows, and will become apparent from the description, or may be learned by practice of the application.

Description of drawings

The above and/or additional aspects and advantages of the present application will become apparent and easy to understand from the following description of the embodiments in conjunction with the accompanying drawings, wherein:

FIG. 1 is a schematic diagram of a solution using switch port mirroring traffic in the related art;

Fig. 2 is a schematic flow chart of a performance testing method provided by the embodiment of the present application;

Fig. 3 is a schematic diagram of a performance testing scheme provided by the embodiment of the present application;

FIG. 4 is a schematic diagram of a performance testing scheme provided in the embodiment of the present application;

FIG. 5 is a schematic structural diagram of a performance testing device provided in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of an electronic device for performance testing provided by an embodiment of the present application.

Detailed ways

Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the figures are exemplary only for explaining the present application, and are not construed as limiting the present application.

Those skilled in the art will understand that unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the word "comprising" used in the description of the present application refers to the presence of features, integers, steps, operations, elements and/or components, but does not exclude the presence or addition of one or more other features, integers, Steps, operations, elements, components and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Additionally, "connected" or "coupled" as used herein may include wireless connection or wireless coupling. The expression "and/or" used herein includes all or any elements and all combinations of one or more associated listed items.

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

The technologies, terms, etc. involved in this application will be described below.

Load balancing device: It is a network service device that distributes traffic to multiple back-end servers. In an application system implemented based on server clusters, traffic distribution can be used to rapidly improve the external service capability of the application system. In addition, the load balancing device is also called "four-to-seven-layer switch". Among them, the four-layer load balancing mainly determines the final selected internal server through the target address and port in the message, combined with the server selection method of the load balancing device; Layer-7 load balancing mainly determines the final selected internal server through the content of the application layer in the message, combined with the server selection method set by the load balancing device. That is to say, seven-layer load balancing works at the application layer of the OSI model (Open System Interconnection Reference Model, Open System Interconnection Communication Reference Model), and is based on a virtual URL (uniform resource locator, uniform resource locator) or host IP (Internet Protocol, Internet Protocol) load balancing.

Online traffic: that is, real traffic. Since the pre-release environment requires real traffic for functional regression and verification, for some applications that require high availability and business fault tolerance, real traffic can be used for testing.

HTTPS (Hyper Text Transfer Protocol over SecureSocket Layer) is an HTTP channel aimed at security. On the basis of HTTP, the security of the transmission process is guaranteed through transmission encryption and identity authentication.

In the performance test of load balancing equipment, due to the complex online user access behavior, offline simulation is difficult to keep consistent with user behavior, resulting in unrealistic offline simulation, and limited offline simulation scenarios, which may lead to incomplete business coverage Therefore, online traffic is an important content for load balancing device application testing, but it is difficult for the offline test environment to fully simulate the online operating environment. In the related technology, in order to be able to test in reality, a scheme of using switch port mirroring traffic is provided, which copies the traffic of the online gateway to the test gateway node by setting the traffic control policy on the mirroring switch to realize Layer 4 online traffic replication.

However, as shown in Figure 1, if the switch port mirroring traffic solution is also used to replicate online traffic for Layer 7 load balancing, most of the traffic uses the HTTPS protocol, and the HTTPS protocol requires the server and the client to generate a Random number (key), which will cause the server key in the test environment and the online environment to be inconsistent, so the HTTPS traffic cannot actually establish a connection with the load balancing device in the test environment, making this solution unsuitable for Layer 7 load balancing copy of online traffic.

Aiming at at least one of the above-mentioned technical problems existing in the prior art or areas that need to be improved, this application proposes a performance testing method, which simulates online traffic by automatically parsing the online logs of the load balancing device to complete the load balancing device performance testing. The solution provided in this application can be understood as a supplement to the inability to implement HTTPS traffic connection establishment in the switch port mirroring method. The implementation of the technical solution of this application only needs to provide the online log of the load balancing device to realize batch traffic replication. After traversing the log files of the load balancing device (as recorded in the log data when running online in the test environment Behavioral data), and determine the result of the performance test by checking whether the load balancing device is abnormal. This technical solution is beneficial to reduce the test cost, improve the test efficiency, and save the test time.

The solutions provided in the embodiments of the present application relate to equipment performance testing technologies, which are specifically described through the following embodiments.

The technical solution of the present application and how the technical solution of the present application solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below in conjunction with the accompanying drawings.

Those skilled in the art can understand that the "terminal" used here can be a mobile phone, a tablet computer, a PDA (Personal Digital Assistant, a personal digital assistant), a MID (Mobile Internet Device, a mobile Internet device), etc.; It can be realized by an independent server or a server cluster composed of multiple servers.

A possible implementation is provided in the embodiment of the present application. As shown in FIG. 2, a performance testing method is provided, which may include the following steps S101-S104:

Step S101: Obtain a log file; the log file includes log data when the load balancing device is running.

Specifically, the log file (log file) can be obtained from the load device in the online operating environment, or can be obtained from the log server Log server used to store the load balancing device; wherein, the online operating environment can be a load Balance the environment in which the equipment is placed in the actual application of the application system. However, the embodiment of the present application may be implemented in an offline test environment, that is, the environment in which the performance test of the load balancing device is performed.

Wherein, the log file acquired in step S101 includes multiple items, and each log file includes corresponding log data when the load balancing device processes a certain request in the online environment. Wherein, the Log server can support functions such as tracking logs, viewing by page, and downloading files. Therefore, in this embodiment of the present application, the log files of the load balancing device can be obtained through the Log server. Wherein, as shown in FIG. 4, the Log server may constitute a part of the log system.

In the embodiment of the present application, the executed main program obtains log files related to case runtime in the log system, and the log files are also log files, which record the interaction information between the system providing the service and the user. The log file may include certain operations of the operation object and the aggregated data of its operation results sorted by time; for example, for web search, the log file may record whether a user who uses a web search engine to search for information interacts with the web searcher during the search for information. The engine interaction process (recorded content may include but not limited to user information, service provision time, service error information).

Step S102: Analyze the log file to obtain key information related to the user request.

Specifically, parsing the log file may refer to performing parsing processing on the log file acquired in step S101, for example, parsing the original log format in a regular manner to make the log data structured. For example, in the parsing process, the corresponding address location, latitude and longitude and other information can be parsed according to the IP field; in this application, key information related to the user request can be obtained by parsing the log file.

Step S103: Send a test request to the load balancing device based on the key information.

Specifically, when sending a test request to the load balancing device based on key information, an HTTP/HTTPS request can be constructed through a request tool based on the key information, and the constructed request can be regarded as a test request, and sent to the load balancing device in the test environment send. It is understandable that this process records requests related to online user access behavior in the simulated log file, and sends the simulated test request to the load balancing device in the test environment to view the load balancing in the test environment. The behavior of the application while the device is processing the test request.

Step S104: Based on the running state of the load balancing device when processing the test request, determine the performance of the load balancing device.

Specifically, in the embodiment of the present application, after processing the test request through the load balancing device, check the load balancing device. If the inspection finds that the load balancing device has problems such as crashes and freezes when processing the test request, and the running status is abnormal, you can Determine that the load balancing device has not passed the current performance test, that is, the performance of the load balancing device is not up to standard; That is, the performance of the load balancing device meets the standard.

The performance test method provided by the embodiment of the present application can be applied to an offline test environment, and the performance test of the load balancer device is completed by simulating online traffic by automatically parsing the log file (log data at runtime) of the load balancer device. The implementation of the method reduces the difference between the offline test environment and the online operating environment, which is beneficial to improving the accuracy of the test, reducing the test cost and improving the test efficiency.

The specific process of traversing all log files in this application will be described below.

In one embodiment, as shown in FIG. 3, the content executed from step S102 to step S103 is to traverse the log file; specifically, the log file is parsed in step S102 to obtain key information related to the user request, including the following steps A1- A2:

Step A1: For each log file, obtain the log information corresponding to the log attribute in the preset log template.

Specifically, it can be understood that the acquired log files may exist in an unstructured data format, and this application may format the log files through a preset log template, that is, convert unstructured log data into structured standardized log data. Among them, the preset log template can be customized according to application requirements. In the embodiment of the present application, considering the need to simulate online user requests to construct test requests, therefore, the log corresponding to the information required for constructing test requests can be Property pre-sets the log template used. Wherein, the log attribute may include information such as IP address, time, user name, domain name, request protocol, and user agent.

Optionally, the preset log template may also include a custom-set log format (such as the format adopted by various log analysis tools), a format displayed on the screen (such as displayed on the screen in the form of a table or a list) log information), log level (such as fatal error FATAL, general error ERROR, warning WARN, general information INFO, debugging information DEBUG, etc.) and other information. The following is an example of the acquired log information corresponding to the log attributes in the preset log template in conjunction with Table 1:

Assume that a certain log file A currently obtained (corresponding to the log information with the serial number 1 in Table 1) is: Jan 1812:09:07shgh01-cp-netproxy124102.shgh01.ksyun.com tengine:2021-01-18T12:09:07 +08:00218.28.204.55:48108120.92.172.246:443172.18.1.11:91000.0490.049200200321156"POSThttps://ipay.cloudwalk.cn/restaurant/api/order/initialOrder HTTP/1.1""-"10"okhttp/ .

Table 1

Specifically, the items in the first row in Table 1 correspond to the various log attributes in the preset log template; among them, the "..." in the last column of the first row indicates that the same preset log template can also be used for requirements Set other logging properties. Wherein, the log information corresponding to the row with the serial number 1 is the log information obtained from the above log file A. Wherein, the serial number N may indicate that there are N log files currently acquired, and the row "xxx" indicates the log information acquired in the corresponding log file N.

Step A2: Filter each log information to obtain key information related to the user request.

Specifically, the key information related to the user request may be based on parameter settings required for constructing the test request. Wherein, the key information may include at least one of the following: request length, HTTP request method, request protocol (such as HTTP/HTTPS), request header Host field, uniform resource identifier (Uniform Resource Identifier, URI), user agent information (User_agent information ).

Assuming that the request length, http request method, protocol, requested url, host and uri, and user agent information in the log attributes are used when constructing the test request, the corresponding information is directly obtained in each log information. Combined with the example shown in Table 1 above, for the log information corresponding to serial number 1, perform step A2 to obtain the following key information:

Request length: 321;

HTTP request method: POST;

Protocol: https:

Requested url, host and uri:

ipay.cloudwalk.cn/restaurant/api/order/initialOrder;

User agent information: okhttp/3.10.0.

In one embodiment, after parsing the log files, configuration files corresponding to each log file can be obtained (the log information, key information, etc. described in the foregoing embodiments can be stored in the configuration file); optionally, as shown in Figure 4 As shown, in the embodiment of the present application, after the online log file is obtained, each line of log may be used as a log file, and the log file may be analyzed.

In one embodiment, as shown in FIG. 4 , in order to further improve the efficiency of the test and avoid deviations in the performance test results due to errors in the information recorded in the log information in the log file, each log information is screened in step A2, Before obtaining the key information related to the user request, the legality of the log information in each log file is also checked, specifically including steps A3-A4:

Step A3: Check the validity of the log information in the log file.

Step A4: Delete the log files that fail the legality check.

Specifically, after obtaining the log information corresponding to each log file, the log information in the log file is checked for legality, and only when the log file passes the legality check, the subsequent steps are performed; otherwise, delete log file, and check the validity of the log information in the next log file.

In a feasible embodiment, the log information in the log file is checked for legality in step A3, including the following steps A31-A33:

Step A31: Check the validity of the log information in the log file based on the preset abnormal label;

Step A32: If it is determined that the log information in the log file carries information corresponding to the preset abnormal label, then it is determined that the log file has not passed the legality check;

Step A33: If it is determined that the log information in the log file does not carry information corresponding to the preset exception tag, then it is determined that the log file passes the legality check.

Specifically, multiple abnormal labels can be set, and then the log information can be checked based on the abnormal labels (for example, it can be realized by an algorithm model of supervised learning). Among them, the abnormal label can be set for the information included in the log attribute or the preset log template. For example: since different log files may correspond to different log levels, it can be set to only use the log level as general in the embodiment of this application. The log file corresponding to the information INFO simulates the online traffic, so you can set the exception label for the log level, such as setting the exception label 1 to correspond to the log level of fatal error FATAL, and the exception label 2 to correspond to the log level of general error ERROR , Exception label 3 corresponds to the log level of warning WARN, and exception label 4 corresponds to the log level of debugging information DEBUG; when performing a legality check, the log information in the log file whose log attribute is the log level is compared with the set exception labels Perform comparison, if the log information corresponds to any abnormal label, it is determined that the log file has not passed the legality check; if the log information does not correspond to any abnormal label, then it is determined that the log file has passed the legality check.

Optionally, the embodiment of the present application may also output the check result when performing the legality check based on step A31, for example, when it is determined that the log information in the log file contains information corresponding to the preset abnormal tag, output the information corresponding to at least one abnormal tag Corresponding log information; if it is determined that the log information in the log file does not carry the information corresponding to the preset exception label, the output is an empty NULL check result. On this basis, when making a judgment on whether to pass the legality check, it can also be based on whether the check result is empty NULL; if the check result is empty NULL, then determine that the corresponding log file has passed the legality check; if the check result is not empty NULL, it is determined that the corresponding log file has failed the legality check.

In a feasible embodiment, the log information in the log file is checked for legality in step A3, including the following steps A34-A36:

Step A34: Estimate the abnormal probability that the log information in the log file includes abnormal information;

Step A35: If the abnormal probability is greater than the preset probability, determine that the log file has not passed the legality check;

Step A36: If the abnormality probability is less than or equal to the preset probability, determine that the log file has passed the legality check.

Specifically, the abnormal information may include at least one of preset keywords, variable abnormal information, and distribution abnormal information. Among them, the preset keyword can represent the log file that needs to be excluded in the requirement. For example, if you want to exclude the log file corresponding to the status code 202, you can set the keyword as 202. Among them, the log information is a variable in the log file. Therefore, the variable abnormal information can refer to the log information that the information represented is abnormal; for example, for the log attribute "protocol", the log information corresponding to the protocol in a log file is When NULL is empty, it can be determined that the log information is variable exception information. Among them, the abnormal distribution information may refer to log information that does not match the log attribute; for example, when the log attribute is "http request method", and the log information in a log file is "https", it can be determined that the log information is abnormal distribution information.

Optionally, a machine learning algorithm can be used to estimate the abnormal probability of the log information in the log file including abnormal information, such as through clustering, PCA (Principal Component Analysis, principal component analysis) and other algorithm models, and output every The abnormal probability corresponding to each log file, and if the abnormal probability is greater than the preset probability, it is determined that the corresponding log file has not passed the legality check; when the abnormal probability is less than or equal to the preset probability, it is determined that the corresponding log file has passed Legality check.

Optionally, weight coefficients can also be set for each item of abnormal information, and the abnormal probability is calculated based on the dimensions of the log information including the abnormal information in the log file and the weight coefficients corresponding to each item of abnormal information. For example: Assume that the default probability is 0.3 and the weight coefficient corresponding to the preset keyword is set to 0.5, the weight coefficient corresponding to variable abnormal information is 0.3, and the weight coefficient corresponding to distribution abnormal information is 0.2; one of the log files When the log information includes 3 preset keywords, a variable abnormal information, and no distribution abnormal information, the corresponding abnormal probability is: 0.45 (0.5*3+0.3*1+0.2*0); then the abnormal probability can be determined Greater than the preset probability, the log file fails the legality check.

Optionally, the legitimacy check can also be implemented through a filter. Before screening key information, log information irrelevant to requirements is filtered out through the filter, so as to further improve the efficiency of performance testing. For example, it can be a level filter (also known as a level filter), delete log files that meet the filter level, and retain log files that do not meet the filter level.

The following describes the specific process of sending a test request to the load balancing device based on key information.

In one embodiment, in step S103, a test request is sent to the load balancing device based on key information, including steps B1-B2:

Step B1: Generate a file transfer curl command based on the key information corresponding to each log file through the preset request construction tool.

Step B2: Send a test request to the load balancing device based on the curl command.

Specifically, the preset request construction tool can be tools such as curl, through which curl commands and requests (such as constructed messages) are generated based on key information; as shown in Figure 4, curl( The full name is CommandLine URL or CommandLine Uniform Resource Locator) command; among them, the curl command works in the command line mode, and uses the URL syntax to transmit data or file transmission. Optionally, when constructing the test request, it can also be combined with the service port number port and virtual IP address (virtual_ip, VIP) that the load balancing device monitors.

For example: based on the key information corresponding to the above log file A, you can use the curl tool to construct a message in combination with the IP address (such as 10.111.76.129) and port (such as 8080) monitored by the load balancing device:

curl-X POST --url "https://10.111.76.129:8080/ipay.cloudwalk.cn/restaurant/api/order/initialOrder" --user-agent "okhttp/3.10.0" --data′** *****.....******′*

Among them, the message length is 321, and the data carried in the message length is replaced with "*", that is, the desensitization process is performed.

Optionally, using the curl command to send the test request may be an HTTP POST request (for submitting data).

The specific processing process of determining the performance of the load balancing device based on the running status of the load balancing device when processing the test request in this application will be described below.

In one embodiment, as shown in FIG. 3, the content executed in step S104 is to check the device; specifically, in step S104, based on the running status of the load balancing device when processing the test request, the performance of the load balancing device is determined, including the following Steps C1-C4:

Step C1: After the load balancing device processes the test requests corresponding to each log file, obtain the running status information of the load balancing device.

Wherein, the running state information includes at least one of a state file and a core dump file. The status file is used to record the information when the load balancing device is running normally; the kernel dump file is used to record the information when the load balancing device is running abnormally.

Specifically, in the embodiment of the present application, when the load balancing device is stuck and other running status is abnormal, it can actively discard the thread whose running status is abnormal, and generate a coredump file; if the load balancing device is obtained The corresponding coredump file is found when the running status information is displayed, and the abnormality of the load balancing device can be checked by analyzing the coredump file. Optionally, in the coredump file, the running state of the thread is recorded, and different running states may be identified by setting labels. If the label corresponding to the abnormal operation status is found in the coredump file, that is, the operation status information indicates that the operation status of the load balancing device is abnormal; if no label corresponding to the abnormal operation status is found in the coredump file , that is, the running status indicates that the running status of the load balancing device is normal.

Specifically, the state file may be a file with a preset numerical size, such as a file of 0k, and the generation of the state file indicates that the load balancing device is in a normal operating state when processing a certain test request.

Step C2: Determine the running state of the load balancing device when processing the test request based on the running state information.

Step C3: If the running state of the load balancing device is abnormal, it is determined that the performance does not meet the standard (fails the test).

Step C4: If the running state of the load balancing device is normal, it is determined that the performance is up to standard (passed the test).

Specifically, in this embodiment of the present application, the performance test result of the load balancing device can be finally determined after the load balancing device has processed all test requests; that is, the performance test result of the load balancing device can be determined after traversing all log files. It is also possible to obtain the running status information synchronously after each load balancing device has processed one or multiple test requests with a set value, and determine the performance test results of the load balancing device, and stop when it is determined that the load balancing device has failed the performance test. Traverse subsequent log files to improve the efficiency of performance testing and reduce the cost of performance testing.

Optionally, in step C2, based on the running state information, determining the running state of the load balancing device when processing the test request includes at least one of the following steps C21-C23:

Step C21: Determine the running state of the load balancing device when processing the test request based on whether the running state information includes a core dump file; if the running state information does not include a core dump file, determine that the running state of the load balancing device is normal; if the running state information Including the core dump file, it is determined that the operating status of the load balancing device is abnormal.

Specifically, in this embodiment of the application, the core dump file is only generated when the load balancing device is running abnormally. When the running state information only includes the coredump file, that is, when the obtained running state information is null, the representation If the running state of the load balancing device is normal, it can be directly determined that the performance of the load balancing device is up to standard; when the obtained running state information includes the coredump file, it indicates that the running state of the load balancing device is abnormal, and it can be directly determined that the performance of the load balancing device is not up to standard .

Step C22: Based on the ratio of the number of files in the state file to the number of requests for the test request, determine the running status of the load balancing device when processing the test request; if the ratio is greater than or equal to the preset ratio, determine that the running status of the load balancing device is normal; if If the ratio is smaller than the preset ratio, it is determined that the operating state of the load balancing device is abnormal.

Specifically, the generation of the status file may indicate that the load balancing device is running normally when processing the corresponding test request. Based on this, after the load balancing device processes the test requests corresponding to all the log files, the final running status of the load balancing device when processing the test requests can be determined based on the ratio of the number of state files to the number of test requests.

For example: Assuming that the preset ratio is 0.76, the number of test requests is 10000, and the number of status files is 8000, the ratio of the number of status files to the number of test requests is 0.8 (8000/10000), then both If the ratio is greater than the preset ratio, it can be determined that the load balancing device is operating normally.

Step C23: Based on the weight coefficients corresponding to the state files and core dump files and the proportion of the number of files in the running state information, determine the corresponding compliance value of the load balancing device when processing the test request; if the compliance value is less than the preset compliance threshold , it is determined that the load balancing device is running abnormally; if the up-to-standard value is greater than or equal to the preset up-to-standard threshold, it is determined that the load balancing device is running normally.

Specifically, the state file whose file size is a preset value may be a state file whose file size is 0k. Corresponding weight coefficients can be set for status files and coredump files respectively. For example, the weight coefficient corresponding to status files is 0.3, and the weight coefficient corresponding to coredump files is 0.7; The ratio is weighted and calculated to determine the up-to-standard value corresponding to the running status information. Assuming that the status file includes 30 and the coredump file includes 10, the ratio of the number of status files is 0.75, and the ratio of the number of coredump files is 0.25; at this time, the up-to-standard value of the load balancing device represented by the running status information can be calculated = 0.3*0.75 +0.7*0.25=0.4. At this point, you can compare the up-to-standard value with the preset up-to-standard threshold. If it is less than the pre-set up-to-standard threshold, the running status information indicates that the load balancing device is running abnormally; if it is greater than or equal to the preset up-to-standard threshold, the running status indicates that the load balancing device The equipment operation status is normal.

Optionally, the calculated up-to-standard value can also be directly output to feed back the current performance status of the load balancing device.

A possible implementation is provided in the embodiment of the present application. As shown in FIG. 5, a performance testing device 500 is provided, and the performance testing device 500 may include: a log acquisition module 501, a log parsing module 502, and a request sending module 503. A performance determination module 504.

Wherein, the log obtaining module 501 is used to obtain the log file; the log file includes the log data when the load balancing device is running; the log analysis module 502 is used to analyze the log file to obtain key information related to the user request; the request sending module 503 uses The method is to send a test request to the load balancing device based on the key information; the performance determining module 504 is configured to determine the performance of the load balancing device based on the running state of the load balancing device when processing the test request.

Optionally, when the log parsing module 502 is configured to perform parsing of log files and obtain key information related to user requests, it is specifically used for:

For each log file, obtain the log information corresponding to the log attribute in the preset log template;

Screen each log information to obtain key information related to user requests.

Optionally, the log parsing module 502 is configured to filter each log information, and before obtaining key information related to the user request, it is also configured to:

Check the validity of the log information in the log file;

Delete log files that fail the legality check.

Optionally, when the log parsing module 502 is used to perform a legality check on the log information in the log file, it is specifically used for:

Check the validity of the log information in the log file based on the preset exception label;

If it is determined that the log information in the log file carries information corresponding to the preset abnormal label, it is determined that the log file has not passed the legality check;

If it is determined that the log information in the log file does not carry information corresponding to the preset exception tag, it is determined that the log file passes the legality check.

Optionally, when the log parsing module 502 is used to perform a legality check on the log information in the log file, it is specifically used for:

The log information in the estimated log file includes the abnormal probability of abnormal information; the abnormal information includes: at least one of preset keywords, variable abnormal information, and distribution abnormal information;

If the abnormal probability is greater than the preset probability, it is determined that the log file has not passed the legality check;

If the abnormality probability is less than or equal to the preset probability, it is determined that the log file passes the legality check.

Optionally, when the request sending module 503 is configured to send a test request to the load balancing device based on key information, it is specifically used for:

Generate a file transfer curl command based on the key information corresponding to each log file through the preset request construction tool;

Send a test request to the load balancing device based on the curl command.

Optionally, the performance determining module 504 is configured to determine the performance of the load balancing device based on the running state of the load balancing device when processing the test request, specifically for:

After the load balancing device processes the test requests corresponding to each log file, obtain the running status information of the load balancing device;

Determine the running status of the load balancing device when processing the test request based on the running status information;

If the operating status of the load balancing device is abnormal, it is determined that the performance is not up to standard;

If the running status of the load balancing device is normal, it is determined that the performance is up to standard.

Optionally, the running state information includes at least one of a state file and a core dump file; the state file is used to record information when the load balancing device is running normally; the core dump file is used to record the load balancing device running as Abnormal information; wherein, the performance determination module is used to determine the operating status of the load balancing device when processing the test request based on the operating status information, specifically for:

Determine the running status of the load balancing device when processing test requests based on whether the running status information includes a core dump file; if the running status information does not include a core dump file, determine that the running status of the load balancing device is normal; if the running status information includes a kernel dump Store files to determine that the operating status of the load balancing device is abnormal;

And/or, based on the ratio of the number of files in the status file to the number of requests for the test request, determine the running status of the load balancing device when processing the test request; if the ratio is greater than or equal to the preset ratio, determine that the running status of the load balancing device is normal; If the ratio is less than the preset ratio, it is determined that the operating state of the load balancing device is abnormal;

And/or, based on the weight coefficients corresponding to the status file and the core dump file and the proportion of the number of files in the running status information, determine the corresponding standard value of the load balancing device when processing the test request; if the standard value is less than the preset standard Threshold, determine that the operating status of the load balancing device is abnormal; if the compliance value is greater than or equal to the preset compliance threshold, determine that the operating status of the load balancing device is normal.

The performance testing device in the embodiments of the present disclosure can execute a performance testing method provided in the embodiments of the present disclosure, and its implementation principle is similar. The actions performed by the modules in the performance testing devices in the embodiments of the present disclosure are the same as Corresponding to the steps in the performance testing method in each embodiment of the present disclosure, for the detailed functional description of each module of the performance testing device, please refer to the description in the corresponding performance testing method shown above, and will not repeat them here .

Based on the same principle as the method shown in the embodiments of the present disclosure, the embodiments of the present disclosure also provide an electronic device, which may include but not limited to: a processor and a memory; a memory for storing computer An operation instruction; a processor, configured to execute the performance testing method shown in the embodiment by calling the computer operation instruction. Compared with the prior art, the performance test method in this application can simulate the online traffic by analyzing the online log of the load balancing device to complete the performance test of the load balancing device, which is conducive to improving the accuracy of the test and reducing the test cost. Improve testing efficiency.

An optional embodiment provides an electronic device, as shown in FIG. 6 , the electronic device 600 shown in FIG. 6 includes: a processor 601 and a memory 603 . Wherein, the processor 601 is connected to the memory 603 , such as through a bus 602 . Optionally, the electronic device 600 may further include a transceiver 604 . It should be noted that, in practical applications, the transceiver 604 is not limited to one, and the structure of the electronic device 600 does not limit the embodiment of the present application.

The processor 601 can be a CPU (Central Processing Unit, central processing unit), a general-purpose processor, a DSP (Digital Signal Processor, a data signal processor), an ASIC (Application Specific Integrated Circuit, an application specific integrated circuit), an FPGA (Field Programmable Gate Array, field programmable gate array) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor 601 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

Bus 602 may include a path for communicating information between the components described above. The bus 602 may be a PCI (Peripheral Component Interconnect, Peripheral Component Interconnect Standard) bus or an EISA (Extended Industry Standard Architecture, Extended Industry Standard Architecture) bus or the like. The bus 602 can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 6 , but it does not mean that there is only one bus or one type of bus.

Memory 603 may be ROM (Read Only Memory, read-only memory) or other types of static storage devices that can store static information and instructions, RAM (Random Access Memory, random access memory) or other types of memory that can store information and instructions A dynamic storage device can also be EEPROM (Electrically Erasable Programmable Read Only Memory, Electrically Erasable Programmable Read-Only Memory), CD-ROM (Compact DiscRead Only Memory, CD-ROM) or other CD storage, CD storage (including compact CD, laser discs, compact discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer media, but not limited thereto.

The memory 603 is used to store application program codes for executing the solution of the present application, and the execution is controlled by the processor 601 . The processor 601 is configured to execute the application program code stored in the memory 603, so as to implement the content shown in the foregoing method embodiments.

Among them, electronic devices include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDA (Personal Digital Assistants), PAD (Tablet Computers), and stationary terminals such as digital TVs, desktop computers, and the like. In addition, the electronic device can also be a server, and the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also provide cloud services, cloud databases, cloud computing, cloud functions, cloud Cloud servers for basic cloud computing services such as storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network, content distribution network), and big data and artificial intelligence platforms, but this application does not limited to this. The electronic device shown in FIG. 6 is only an example, and should not limit the functions and application scope of the embodiments of the present disclosure.

An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when it is run on a computer, the computer can execute the corresponding content in the foregoing method embodiments. Compared with the prior art, the performance test method in this application can simulate the online traffic by analyzing the log data of the load balancing device to complete the performance test of the load balancing device, which is conducive to improving the accuracy of the test and reducing the test cost , improve test efficiency.

It should be understood that although the various steps in the flow chart of the accompanying drawings are displayed sequentially according to the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the order of execution is also It is not necessarily performed sequentially, but may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

It should be noted that the above-mentioned computer-readable medium in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can transmit, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted by any appropriate medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device, or may exist independently without being incorporated into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device is made to execute the methods shown in the above-mentioned embodiments.

An embodiment of the present application provides a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method steps provided in the foregoing embodiments.

Computer program code for carrying out the operations of the present disclosure can be written in one or more programming languages, or combinations thereof, including object-oriented programming languages—such as Java, Smalltalk, C++, and conventional Procedural Programming Language - such as "C" or a similar programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through an Internet service provider). Internet connection).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code that contains one or more logical functions for implementing specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified functions or operations , or may be implemented by a combination of dedicated hardware and computer instructions.

The modules involved in the embodiments described in the present disclosure may be implemented by software or by hardware. Wherein, the name of the module does not constitute a limitation of the module itself under certain circumstances, for example, the log acquisition module may also be described as "a module for acquiring log files".

The above description is only a preferred embodiment of the present disclosure and an illustration of the applied technical principles. Those skilled in the art should understand that the disclosure scope involved in this disclosure is not limited to the technical solution formed by the specific combination of the above-mentioned technical features, but also covers the technical solutions formed by the above-mentioned technical features or Other technical solutions formed by any combination of equivalent features. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

Claims (11)

1. A performance testing method, characterized in that, comprising: Obtain a log file; the log file includes log data when the load balancing device is running; Analyzing the log file to obtain key information related to the user request; sending a test request to the load balancing device based on the key information; Based on the running status of the load balancing device when processing the test request, the performance of the load balancing device is determined. 2. The method according to claim 1, wherein the parsing of the log file obtains key information related to the user request, including: For each of the log files, obtain the log information corresponding to the log attribute in the preset log template; Each of the log information is screened to obtain key information related to the user request. 3. The method according to claim 2, wherein before filtering each of the log information to obtain key information related to the user request, further comprising: Checking the validity of the log information in the log file; Log files that fail the described legality checks are deleted. 4. The method according to claim 3, wherein the checking of the validity of the log information in the log file includes: Check the validity of the log information in the log file based on the preset exception label; If it is determined that the log information in the log file carries information corresponding to the preset abnormal label, then it is determined that the log file has not passed the legality check; If it is determined that the log information in the log file does not carry information corresponding to the preset exception tag, it is determined that the log file passes the validity check. 5. The method according to claim 3 or 4, wherein the checking of the validity of the log information in the log file includes: It is estimated that the log information in the log file includes an abnormal probability of abnormal information; the abnormal information includes: at least one of preset keywords, variable abnormal information, and distribution abnormal information; If the abnormal probability is greater than the preset probability, it is determined that the log file has not passed the legality check; If the abnormal probability is less than or equal to the preset probability, it is determined that the log file passes the legality check. 6. The method according to claim 1, wherein the sending a test request to the load balancing device based on the key information comprises: Generate a file transfer curl command based on the key information corresponding to each log file through the preset request construction tool; Sending a test request to the load balancing device based on the curl command. 7. The method according to claim 1, wherein the determining the performance of the load balancing device based on the operating state of the load balancing device when processing the test request comprises: After the load balancing device processes the test requests corresponding to each log file, obtain the running status information of the load balancing device; determining an operating state of the load balancing device when processing the test request based on the operating state information; If the operating state of the load balancing device is abnormal, it is determined that the performance is not up to standard; If the running state of the load balancing device is normal, it is determined that the performance is up to standard. 8. The method according to claim 7, wherein the running state information includes at least one of a state file and a core dump file; the state file is used to record that the load balancing device running state is normal information at the time; the core dump file is used to record the information when the load balancing device is in an abnormal operating state; The determining the running state of the load balancing device when processing the test request based on the running state information includes: Determine the operating state of the load balancing device when processing the test request based on whether the operating state information includes a core dump file; if the operating state information does not include a core dump file, determine the operating state of the load balancing device is normal; if the running state information includes a kernel dump file, determine that the running state of the load balancing device is abnormal; And/or, based on the ratio of the number of files in the status file to the number of requests for the test request, determine the operating status of the load balancing device when processing the test request; if the ratio is greater than or equal to a preset ratio , determining that the operating state of the load balancing device is normal; if the ratio is less than a preset ratio, determining that the operating state of the load balancing device is abnormal; And/or, based on the respective weight coefficients corresponding to the state file and the core dump file and the proportion of the number of files in the running state information, determine the corresponding standard value of the load balancing device when processing the test request ; If the standard attainment value is less than the preset standard attainment threshold, determine that the load balancing device is running abnormally; if the standard attainment value is greater than or equal to the preset standard attainment threshold, determine that the load balancing device is running normally. 9. A performance testing device, characterized in that, comprising: The log obtaining module is used to obtain log files; the log files include log data when the load balancing device is running; A log parsing module, configured to parse the log file to obtain key information related to the user request; A request sending module, configured to send a test request to the load balancing device based on the key information; A performance determining module, configured to determine the performance of the load balancing device based on the running state of the load balancing device when processing the test request. 10. An electronic device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein any one of claims 1-8 is realized when the processor executes the program The performance test method described. 11. A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the program is executed by a processor, the performance testing method according to any one of claims 1-8 is implemented.

Images