CN115695227A

CN115695227A - Performance test method and device, electronic equipment and readable storage medium

Info

Publication number: CN115695227A
Application number: CN202110831533.4A
Authority: CN
Inventors: 张明昊
Original assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Current assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Priority date: 2021-07-22
Filing date: 2021-07-22
Publication date: 2023-02-03

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 test method and device, electronic equipment and readable storage medium

Technical Field

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

Background

With the continuous development of engineering technology, more and more application systems realized based on server clusters provide services for daily life and work of people. In the application system, a load balancing device, namely a network service device, can be adopted to distribute the flow of a plurality of back-end servers, so that the external service capability of the application system is improved. The performance test is carried out on the load balancing equipment, the processing performance of the equipment is obtained, and the stability of an application system is ensured.

In the related art, when testing the performance of the load balancing device, an offline testing mode is usually adopted, however, the offline testing environment is different from the online running environment where the load balancing device is actually applied, so that the accuracy of the testing result is low, and the testing efficiency is low.

Disclosure of Invention

The purpose of the present application is to solve at least one of the above technical drawbacks, and to provide the following solutions:

in a first aspect, a performance testing method is provided, including:

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 test request is processed.

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

acquiring log information corresponding to log attributes in a preset log template aiming at each log file;

and screening each log information to obtain key information related to the user request.

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

carrying out validity check on the log information in the log file;

and deleting the log files which fail the validity check.

With reference to the second implementation manner of the first aspect, in a third implementation manner of the first aspect, the performing validity check on the log information in the log file includes:

carrying out validity check on log information in the log file based on a preset abnormal label;

if the log information in the log file is determined to carry the information corresponding to the preset abnormal label, determining that the log file does not pass the validity check;

and if the log information in the log file is determined not to carry the information corresponding to the preset abnormal label, determining that the log file passes the validity check.

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

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

if the abnormal probability is larger than the preset probability, determining that the log file does not pass the validity check;

and if the abnormal probability is less than or equal to the preset probability, determining that the log file passes the validity 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 critical information includes:

generating a file transmission curl command based on key information corresponding to each log file through a preset request construction tool;

and sending a test request to the load balancing equipment based on the curl command.

With reference to the first aspect, in a sixth implementation manner of the first aspect, the determining, based on the operation state of the load balancing apparatus when processing the test request, the performance of the load balancing apparatus includes:

after the load balancing equipment processes the test requests corresponding to the log files respectively, acquiring the running state information of the load balancing equipment;

determining the running state of the load balancing equipment when the test request is processed based on the running state information;

if the running state of the load balancing equipment is abnormal, determining that the performance does not reach the standard;

and if the running state of the load balancing equipment is normal, determining that the performance reaches the standard.

With reference to the sixth implementation manner of the first aspect, in a seventh implementation manner of the first aspect, the running state information includes at least one of a state file and a kernel dump file; the state file is used for recording information when the running state of the load balancing equipment is normal; the kernel dump file is used for recording information when the running state of the load balancing equipment is abnormal;

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

determining the running state of the load balancing equipment when processing the test request based on whether the running state information comprises a kernel dump file; if the running state information does not comprise a kernel dump file, determining that the running state of the load balancing equipment is normal; if the running state information comprises a kernel dump file, determining that the running state of the load balancing equipment is abnormal;

and/or determining the running state of the load balancing equipment when processing the test request based on the ratio of the file number of the state file to the request number of the test request; if the ratio is greater than or equal to a preset ratio, determining that the running state of the load balancing equipment is normal; if the ratio is smaller than a preset ratio, determining that the running state of the load balancing equipment is abnormal;

and/or determining a corresponding standard value of the load balancing equipment when processing the test request based on the weight coefficient respectively corresponding to the state file and the kernel dump file and the proportion of the number of files in the running state information; if the standard value is smaller than a preset standard threshold value, determining that the running state of the load balancing equipment is abnormal; and if the standard reaching value is larger than or equal to a preset standard reaching threshold value, determining that the running state of the load balancing equipment is normal.

In a second aspect, a performance testing apparatus is provided, comprising:

the log acquisition module is used for acquiring a log file; the log file comprises log data of the load balancing equipment during operation;

the log analysis module is used for analyzing 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;

and the performance determining module is used for determining the performance of the load balancing equipment based on the running state of the load balancing equipment when the test request is processed.

In a third aspect, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer 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, on which a computer program is stored, which when executed by a processor implements the performance testing method shown in the first aspect of the present application.

The beneficial effect that technical scheme that this application provided brought is:

after the log file is obtained, the log file is analyzed, and then after key information related to a user request is obtained, a test request is sent to the load balancing equipment based on the key information, and then the performance of the load balancing equipment is determined based on the running state of the load balancing equipment when the test request is processed; the log file comprises log data of the load balancing device during operation, namely the online performance test of the load balancing device can be completed by analyzing the log file of the load balancing device to simulate the online flow, so that the difference between an online test environment and an online operation environment where the load balancing device is actually applied can be effectively reduced, the accuracy of an offline test result is improved, the test cost is reduced, and the test efficiency is improved.

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

Drawings

The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

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

fig. 2 is a schematic flowchart of a performance testing method according to an embodiment of the present application;

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

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

FIG. 5 is a schematic structural diagram of a performance testing apparatus according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an electronic device for performance testing according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.

As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude 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. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.

To make the objects, technical solutions and advantages of the present application more clear, the following detailed description of the embodiments of the present application will be made with reference to the accompanying drawings.

The following is a description of the techniques, terms, and the like involved in the present application.

The load balancing device: the network service equipment is used for carrying out flow distribution on a plurality of back-end servers. In an application system realized based on a server cluster, the capacity of the application system for external services can be rapidly improved through flow distribution. In addition, the load balancing device is also called as a four-to seven-layer switch, wherein the four-layer load balancing mainly determines the finally selected internal server by combining a target address and a port in a message and a server selection mode of the load balancing device; the seven-layer load balancing mainly determines the finally selected internal server by the application layer content in the message and the selection mode of the server set by the load balancing equipment. That is, the seven-layer load balancing works in an application layer of an OSI Model (Open System Interconnection Reference Model), and is based on load balancing of a virtual URL (uniform resource locator) or a host IP (Internet Protocol).

On-line flow: i.e. the real traffic. Because the pre-distribution environment needs regression and verification of real flow with work performance, for some applications with higher requirements on availability and service fault tolerance, the real flow can be adopted for testing.

HTTPS (Hyper Text Transfer Protocol over secure token Layer) is an HTTP channel that targets security, and guarantees security of a transmission process through transmission encryption and identity authentication on the basis of HTTP.

In the performance test of the load balancing device, because the access behavior of the online user is complex, the online simulation is difficult to keep consistent with the user behavior, so that the online simulation is not real enough, and the online simulation scene is limited, and the situation of incomplete service coverage may occur, so the online flow is an important content for the application program test of the load balancing device, but the online test environment is difficult to completely simulate the online running environment. In the related art, in order to perform a test truly, a scheme of using a switch port mirror flow is provided, in which a flow control policy is set on a mirror switch, and a flow of an online gateway is copied to a test gateway node, so as to implement four-layer online flow replication.

However, as shown in fig. 1, if the scheme of mirroring traffic at a switch port is also adopted to perform online traffic replication for seven-layer load balancing, since most of the traffic uses the HTTPS protocol, and the HTTPS protocol requires a server and a client to generate a random number (key), a situation that a server key of a test environment is inconsistent with a server key of the online environment occurs, and thus HTTPS traffic cannot be actually established with a load balancing device of the test environment, which results in that the scheme is not suitable for the online traffic replication for seven-layer load balancing.

In order to solve at least one technical problem or a place needing improvement in the prior art, the application provides a performance test method, which simulates online traffic to complete a performance test on a load balancing device by automatically analyzing an online log of the load balancing device. The scheme provided by the application can be understood as a supplement that the HTTPS traffic connection establishment cannot be realized by the switch port mirroring method. According to the technical scheme, batch flow replication can be achieved only by providing the online logs of the load balancing equipment, and after the log files of the load balancing equipment are traversed (such as behavior data recorded by log data during online running in a test environment), the result of performance test is determined by checking whether the load balancing equipment is abnormal.

The scheme provided by the embodiment of the application relates to a device performance testing technology, and is specifically explained by the following embodiment.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Those skilled in the art will understand that the "terminal" used herein may be a Mobile phone, a tablet computer, a PDA (Personal Digital Assistant), an MID (Mobile Internet Device), etc.; a "server" may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.

A possible implementation manner is provided in the embodiment of the present application, and as shown in fig. 2, a performance testing method is provided, which may include the following steps S101 to S104:

step S101: acquiring a log file; the log file includes log data of the load balancing device during operation.

Specifically, a Log file (Log file) may be obtained from a load device in an online operating environment, or may also be obtained from a Log server for storing a load balancing device; the online running environment may be an environment in which the load balancing device is located when the application system is actually applied. The embodiment of the application can execute the offline test environment, namely the environment where the load balancing equipment is subjected to performance test.

The log file obtained in step S101 includes multiple log files, and each log file includes log data corresponding to a load balancing device when processing a request in an online environment. The Log server can support functions of tracking logs, checking pages, downloading files and the like, and therefore the Log file of the load balancing device can be obtained through the Log server in the embodiment of the application. Where the Log server may form part of a Log system, as shown in fig. 4.

In the embodiment of the application, the executed main program obtains a log file related to a case runtime in a log system, where the log file is also a log file, and records information of interaction between a system providing a service and a user. The log file may include collection data in which some operations of the operation objects and operation results thereof are sorted by time; for example, for a web search, the log file may record the process that a user searching for information using a web search engine interacts with the web search engine during the search of information (the recorded content may include, but is not limited to, user information, time of providing service, information of service errors).

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

Specifically, analyzing the log file may refer to performing analysis processing on the log file acquired in step S101, for example, analyzing the original log format in a regular manner, so as to structure the log data. If in the analyzing process, the corresponding information such as address position, longitude and latitude and the like can be analyzed according to the IP field; in the application, the key information related to the user request can be acquired by analyzing the log file.

Step S103: and sending a test request to the load balancing equipment based on the key information.

Specifically, when the test request is sent to the load balancing device based on the key information, an HTTP/HTTPs request may be constructed by a request tool based on the key information, and the constructed request may be sent to the load balancing device in the test environment as a test request. It can be understood that the process simulates the requests related to the online user access behavior recorded in the log file, and sends the simulated test requests to the load balancing device in the test environment to view the running condition of the application program when the load balancing device in the test environment processes the test requests.

Step S104: and determining the performance of the load balancing equipment based on the running state of the load balancing equipment when the test request is processed.

Specifically, after the load balancing device processes the test request, the load balancing device is checked, and if the problem that the running state of the load balancing device is abnormal, such as breakdown and blockage, occurs when the load balancing device processes the test request, it can be determined that the load balancing device fails the current performance test, that is, the performance of the load balancing device does not reach the standard; if the operation state of the load balancing device is found to be normal when the test request is processed by the check, it may be determined that the load balancing device passes the current performance test, that is, the performance of the load balancing device reaches the standard.

The performance testing method provided by the embodiment of the application can be applied to an offline testing environment, the online flow is simulated by automatically analyzing the log file (log data during operation) of the load balancing equipment to complete the performance testing of the load balancing equipment, the difference between the offline testing environment and the online operating environment is reduced by implementing the method, the accuracy of the testing is favorably improved, the testing cost is reduced, and the testing efficiency is improved.

The following is a description of a specific process for traversing all log files in the present application.

In an embodiment, as shown in fig. 3, the content executed in steps S102 to S103 is a traversal log file; specifically, the step S102 of parsing the log file to obtain the key information related to the user request includes the following steps A1-A2:

step A1: and acquiring log information corresponding to the log attributes in the preset log template aiming at each log file.

Specifically, it can be understood that the obtained log file may exist in an unstructured data format, and the method and the device may perform formatting processing on the log file through a preset log template, that is, convert unstructured log data into structured log data. In the embodiment of the application, the test request is constructed in consideration of the requirement of simulating the online user request, so that the adopted log template can be preset according to the log attribute corresponding to the information required by constructing the test request. The log attribute may include information such as an IP address, time, user name, domain name, request protocol, user agent, etc.

Optionally, the preset log template may further include a log format (such as formats adopted by various log analysis tools) set by a user, a format displayed on the screen (such as log information displayed on the screen in a table or a list), a log level (such as several levels of FATAL ERROR fault, general ERROR, warning WARN, general information INFO, debugging information DEBUG, and the like), and other information. The following description, with reference to table 1, illustrates the obtained log information corresponding to the log attribute in the preset log template:

assume that a certain currently acquired log file a (corresponding to log information with sequence number 1 in table 1) is: jan 1812.

TABLE 1

Specifically, the items in the top row in table 1 correspond to the log attributes in the preset log template; the 'page-like' in the last column of the first row indicates that other log attributes can be set in the same preset log template according to requirements. The log information corresponding to the row with the sequence number of 1 is the log information obtained from the log file a. The sequence number N may indicate that N log files are currently obtained, and the row "xxx" indicates log information obtained from the corresponding log file N.

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

In particular, the critical information associated with the user request may be based on the parameter settings required to construct the test request. Wherein the key information may include at least one of: request length, HTTP request method, request protocol (e.g., HTTP/HTTPs), request header Host field, uniform Resource Identifier (URI), user agent information (User _ agent information).

When the request length, the http request method, the protocol, the url, the host and the uri of the request and the user agent information are used in the log attribute during the construction of the test request, corresponding information is directly obtained in each log information. With reference to the example shown in table 1, for the log information corresponding to the sequence number 1, the following key information can be obtained by performing step A2:

request length: 321;

the http request method comprises the following steps: POST;

protocol: https:

url, host and uri of request:

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

user agent information: okhttp/3.10.0.

In an embodiment, after the log file is parsed, a configuration file corresponding to each log file may be obtained (the log information, the key information, and the like described in the foregoing embodiment may be stored in the configuration file); optionally, as shown in fig. 4, in the embodiment of the present application, after an online log file is obtained, each row of log may be used as a log file, and the log file may be analyzed.

In an embodiment, as shown in fig. 4, to further improve the testing efficiency and avoid deviation of the performance test result due to an error in the information recorded by the log information in the log file, before the step A2 of screening each log information and obtaining the key information related to the user request, the method further performs validity check on the log information in each log file, and specifically includes the steps A3 to A4:

step A3: and carrying out validity check on the log information in the log file.

Step A4: and deleting the log files which fail to pass the validity check.

Specifically, after the log information corresponding to each log file is obtained, performing validity check on the log information in the log file, and executing the subsequent steps only when the log file passes the validity check; otherwise, deleting the log file and checking the validity of the log information in the next log file.

In a possible embodiment, the step A3 of checking the validity of the log information in the log file includes the following steps a31-a33:

step A31: carrying out validity check on log information in the log file based on a preset abnormal label;

step A32: if the log information in the log file is determined to carry information corresponding to the preset abnormal label, determining that the log file does not pass the validity check;

step A33: and if the log information in the log file is determined not to carry the information corresponding to the preset abnormal label, determining that the log file passes the validity check.

Specifically, a plurality of abnormal labels may be set, and then log information is checked based on the abnormal labels (e.g., may be implemented by an algorithm model of supervised learning). The abnormal label may be set for a log attribute or information included in a preset log template, for example: because different log files may correspond to different log levels, it may be set that only the log level corresponding to the general information INFO is used for performing on-line traffic simulation, and therefore, it may be set that exception labels are set for the log levels, for example, a log level of an exception label 1 corresponding to a FATAL ERROR false, a log level of an exception label 2 corresponding to a general ERROR, a log level of an exception label 3 corresponding to a warning WARN, and a log level of an exception label 4 corresponding to DEBUG information DEBUG are set; when the validity check is carried out, comparing the log information of which the log attribute is the log grade in the log file with the set abnormal labels, and if the log information corresponds to any abnormal label, determining that the log file does not pass the validity check; and if the log information does not correspond to any abnormal label, determining that the log file passes the validity check.

Optionally, in the embodiment of the present application, when performing validity check based on step a31, a check result may also be output, for example, when it is determined that log information in a log file carries information corresponding to a preset abnormal tag, log information corresponding to at least one abnormal tag is output; and if the log information in the log file is determined not to carry the information corresponding to the preset abnormal label, outputting the checking result of NULL. On the basis, when the judgment of whether the validity check is passed is carried out, the judgment can be carried out based on whether the check result is empty NULL; if the check result is NULL, determining that the corresponding log file passes the validity check; and if the checking result is not NULL, determining that the corresponding log file does not pass the validity check.

In a possible embodiment, the step A3 of checking the validity of the log information in the log file includes the following steps a34-a36:

step A34: predicting the abnormal probability that the log information in the log file comprises abnormal information;

step A35: if the abnormal probability is larger than the preset probability, determining that the log file does not pass the validity check;

step A36: and if the abnormal probability is less than or equal to the preset probability, determining that the log file passes the validity check.

Specifically, the abnormal information may include at least one of a preset keyword, variable abnormal information, and distribution abnormal information. The preset keyword may represent a log file that is expected to be excluded from the requirement, and if it is expected to exclude the log file corresponding to the status code 202, the keyword may be set to 202. The log information is a variable in the log file, and therefore, the variable abnormal information may refer to log information in which the represented information is abnormal; if log information corresponding to a protocol in a certain log file is NULL for the log attribute protocol, it can be determined that the log information is variable abnormality information. The distribution abnormal information may refer to log information that does not match with the log attributes; if the log attribute is "http request method", and the log information in a certain log file is "https", it can be determined that the log information is distribution anomaly information.

Optionally, the abnormal probability that the log information in the log file includes the abnormal information may be estimated through a machine learning algorithm, for example, the abnormal probability may be implemented through an algorithm model such as clustering and Principal Component Analysis (PCA), and the like, the abnormal probability corresponding to each log file is output, and the corresponding log file is determined not to pass the validity check under the condition that the abnormal probability is greater than the preset probability; and determining that the corresponding log file passes the validity check under the condition that the abnormal probability is less than or equal to the preset probability.

Optionally, a weight coefficient may be set for each item of abnormal information, and the abnormal probability may be calculated based on the dimension of the abnormal information included in the log information of the log file and the weight coefficient corresponding to each item of abnormal information. For example, the following steps are carried out: assuming that the preset probability is 0.3, and setting the weight coefficient corresponding to the preset keyword to be 0.5, the weight coefficient corresponding to the variable abnormal information to be 0.3, and the weight coefficient corresponding to the distribution abnormal information to be 0.2; when the log information of one log file comprises 3 preset keywords, one piece of variable abnormal information and no distribution abnormal information, the corresponding abnormal probability is as follows: 0.45 (0.5 + 3+0.3 + 1+0.2 + 0); it may be determined that the probability of anomaly is greater than a preset probability and the log file fails the validity check.

Optionally, the validity check may also be implemented by a filter, and before the filtering of the key information, log information irrelevant to the requirement is filtered out by the filter, so as to further improve the efficiency of the performance test. If the log file is a level filter (also called a level filter), the log file meeting the filtering level is deleted, and the log file not meeting the filtering level is reserved.

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

In an embodiment, the sending of the test request to the load balancing device based on the critical information in step S103 includes steps B1-B2:

step B1: and generating a file transmission curl command based on the key information corresponding to each log file through a preset request construction tool.

And step B2: and sending a test request to the load balancing equipment based on the curl command.

Specifically, the preset request construction tool may be a curl or other tool, and a curl command and a request (such as a constructed message) are generated by the curl tool based on the key information; as shown in fig. 4, a curl (called a command URL or a command Uniform Resource Locator) command may be generated based on the filtered key information; the curl command works in a command line mode, and data transmission or file transmission is carried out by using the syntax of the URL. Optionally, when the test request is constructed, the test request may be performed by combining a service port number port, a virtual IP address (VIP), and the like monitored by the load balancing device.

For example, the following steps are carried out: based on the key information corresponding to the log file a, a message may be constructed by using a curl tool in combination with an ip address (e.g., 10.111.76.129) and a port (e.g., 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′*******.....******′*

wherein, the message length is 321, and data carried by the message length is replaced by a "+", that is, desensitization processing is performed.

Alternatively, the send test request using the curl command may be a POST request (for submitting data) of HTTP.

A specific process for determining the performance of the load balancing device based on the operating state of the load balancing device when processing the test request in the present application is described below.

In one embodiment, as shown in fig. 3, the content executed in step S104 is an inspection device; specifically, the determining the performance of the load balancing device in step S104 based on the operation state of the load balancing device when processing the test request includes the following steps C1 to C4:

step C1: and after the load balancing equipment processes the test requests respectively corresponding to the log files, acquiring the running state information of the load balancing equipment.

Wherein the running state information comprises at least one of a state file and a kernel dump file. The state file is used for recording the information when the running state of the load balancing equipment is normal; the kernel dump file is used for recording the information when the running state of the load balancing equipment is abnormal.

Specifically, in the embodiment of the application, when the load balancing device has a problem that the running state is abnormal, such as jamming, the thread with the abnormal running state can be actively discarded, and a kernel dump coredump file is generated; if the corresponding coredump file is found when the running state information of the load balancing equipment is acquired, the abnormal condition of the load balancing equipment can be checked by analyzing the coredump file. Optionally, in the coredump file, the running states of the threads are recorded, and different running states may be identified by setting a tag. If a label corresponding to the abnormal operation state is inquired in the coredump file, the operation state information represents that the operation state of the load balancing equipment is abnormal; if the label corresponding to the abnormal operating state is not found in the coredump file, the operating state represents that the operating state of the load balancing device is normal.

Specifically, the state file may be a file with a preset value size, for example, a file with a value of 0k, and the generation of the state file indicates that the operation state of the load balancing device is normal when processing a certain test request.

And step C2: and determining the operation state of the load balancing equipment when the test request is processed based on the operation state information.

And C3: and if the running state of the load balancing equipment is abnormal, determining that the performance does not reach the standard (fails the test).

And C4: and if the running state of the load balancing equipment is normal, determining that the performance reaches the standard (passes the test).

Specifically, the embodiment of the application can finally determine the performance test result of the load balancing equipment after the load balancing equipment processes all the test requests; that is, after traversing all log files is finished, determining the performance test result of the load balancing equipment. The method also can synchronously acquire the running state information after the load balancing equipment processes a plurality of test requests of one or a set value, determine the performance test result of the load balancing equipment, and stop traversing subsequent log files while determining that the load balancing equipment fails the performance test, so as to improve the efficiency of the performance test and reduce the cost of the performance test.

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

step C21: determining the running state of the load balancing equipment when the test request is processed based on whether the running state information comprises a kernel dump file; if the running state information does not include the kernel dump file, determining that the running state of the load balancing equipment is normal; and if the running state information comprises the kernel dump file, determining that the running state of the load balancing equipment is abnormal.

Specifically, in the embodiment of the present application, the kernel dump file is generated only when the running state of the load balancing device is abnormal, and when the running state information only includes a coredump file, that is, when the obtained running state information is null, it is characterized that the running state of the load balancing device is normal, and it may be directly determined that the performance of the load balancing device reaches the standard; when the obtained running state information comprises the coredump file, the running state of the load balancing equipment is represented to be abnormal, and the performance of the load balancing equipment can be directly determined to be not up to the standard.

Step C22: determining the running state of the load balancing equipment when processing the test request based on the ratio of the number of files of the state file to the number of requests of the test request; if the ratio is larger than or equal to the preset ratio, determining that the running state of the load balancing equipment is normal; and if the ratio is smaller than the preset ratio, determining that the running state of the load balancing equipment is abnormal.

Specifically, the generation of the state file may represent that the operation state of the load balancing device is normal when processing the corresponding test request. Based on this, after the load balancing device has processed the test requests corresponding to all the log files, the operating state finally embodied by the load balancing device when processing the test requests may be determined based on the ratio of the number of files in the state file to the number of requests in the test requests.

By way of example: if the preset ratio is 0.76, the number of requests of the test requests is 10000, and the number of files of the status file is 8000, the ratio of the number of files of the status file to the number of requests of the test requests is 0.8 (8000/10000), and the ratio of the number of files of the status file to the number of requests of the test requests is greater than the preset ratio, it can be determined that the load balancing device operates normally.

Step C23: determining a corresponding standard value of the load balancing equipment when processing the test request based on the weight coefficient respectively corresponding to the state file and the kernel dump file and the file number ratio in the running state information; if the standard value is smaller than the preset standard threshold value, determining that the running state of the load balancing equipment is abnormal; and if the standard value is greater than or equal to the preset standard threshold value, determining that the running state of the load balancing equipment is normal.

Specifically, the state file having the file size of the preset value may be a state file having a file size of 0 k. Corresponding weight coefficients can be set for the state file and the coredump file respectively, for example, the weight coefficient corresponding to the state file is 0.3, and the weight coefficient corresponding to the coredump file is 0.7; the scalar value corresponding to the running state information can be determined by weighting and calculating the ratio of the number of the state files to the number of the coredump files in the running state information. Assuming that the state files comprise 30, the coredump files comprise 10, the ratio of the number of the state files to the number of the coredump files is 0.75, and the ratio of the number of the coredump files to the number of the status files is 0.25; at this time, the standard value =0.3 × 0.75+0.7 × 0.25=0.4 of the load balancing device characterized by the operation status information may be calculated. At this time, the standard reaching value may be compared with a preset standard reaching threshold, and if the standard reaching value is smaller than the preset standard reaching threshold, the running state information represents that the running state of the load balancing device is abnormal; and if the running state is larger than or equal to the preset standard reaching threshold value, the running state represents that the running state of the load balancing equipment is normal.

Alternatively, the computed scalar value may be directly output to feed back the current performance state of the load balancing device.

In an embodiment of the present application, a possible implementation manner is provided, as shown in fig. 5, that is, a performance testing apparatus 500 is provided, where the performance testing apparatus 500 may include: a log obtaining module 501, a log analyzing module 502, a request sending module 503 and a performance determining module 504.

The log obtaining module 501 is configured to obtain a log file; the log file comprises log data of the load balancing equipment during operation; a log analysis module 502, configured to analyze a log file to obtain key information related to a user request; the request sending module 503 is configured to send a test request to the load balancing device based on the key information; a performance determining module 504, configured to determine performance of the load balancing device based on an operating state of the load balancing device when processing the test request.

Optionally, the log parsing module 502 is configured to, when the log file is parsed to obtain key information related to the user request, specifically:

Optionally, the log parsing module 502 is configured to perform screening on each log information, and before obtaining the key information related to the user request, further configured to:

carrying out validity check on log information in the log file;

and deleting the log files which fail to pass the validity check.

Optionally, the log parsing module 502 is configured to, when performing validity check on log information in a log file, specifically:

if the log information in the log file is determined to carry information corresponding to the preset abnormal label, determining that the log file does not pass the validity check;

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

Optionally, the request sending module 503 is configured to, when executing sending the test request to the load balancing device based on the key information, specifically:

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

Optionally, the running state information includes at least one of a state file and a kernel dump file; the state file is used for recording the information when the running state of the load balancing equipment is normal; the kernel dump file is used for recording information when the running state of the load balancing equipment is abnormal; the performance determining module is configured to, when determining an operating state of the load balancing device when processing the test request based on the operating state information, specifically:

determining the running state of the load balancing equipment when the test request is processed based on whether the running state information comprises a kernel dump file; if the running state information does not include the kernel dump file, determining that the running state of the load balancing equipment is normal; if the running state information comprises a kernel dump file, determining that the running state of the load balancing equipment is abnormal;

and/or determining the running state of the load balancing equipment when the test request is processed based on the ratio of the number of files of the state file to the number of requests of the test request; if the ratio is greater than or equal to the preset ratio, determining that the running state of the load balancing equipment is normal; if the ratio is smaller than the preset ratio, determining that the running state of the load balancing equipment is abnormal;

and/or determining a corresponding standard value of the load balancing equipment when processing the test request based on the weight coefficient respectively corresponding to the state file and the kernel dump file and the file number ratio in the running state information; if the standard value is smaller than the preset standard threshold value, determining that the running state of the load balancing equipment is abnormal; and if the standard value is greater than or equal to the preset standard threshold value, determining that the running state of the load balancing equipment is normal.

The performance testing apparatus in the embodiments of the present disclosure may execute a performance testing method provided in the embodiments of the present disclosure, and the implementation principle is similar, the actions executed by each module in the performance testing apparatus in each embodiment of the present disclosure correspond to the steps in the performance testing method in each embodiment of the present disclosure, and for the detailed function description of each module in the performance testing apparatus, reference may be specifically made to the description in the corresponding performance testing method shown in the foregoing, and details are not repeated here.

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

In an alternative embodiment, an electronic device is provided, as shown in fig. 6, the electronic device 600 shown in fig. 6 comprising: a processor 601 and a memory 603. Wherein the processor 601 is coupled to the memory 603, such as via a bus 602. Optionally, the electronic device 600 may also include a transceiver 604. It should be noted that the transceiver 604 is not limited to one in practical applications, and the structure of the electronic device 600 is not limited to the embodiment of the present application.

The Processor 601 may be a CPU (Central Processing Unit), a general-purpose Processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein. The processor 601 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs and microprocessors, and the like.

Bus 602 may include a path that carries information between the aforementioned components. The bus 602 may be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 602 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 6, but this is not intended to represent only one bus or type of bus.

The Memory 603 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these.

The memory 603 is used for storing application program codes for executing the scheme of the application, and the processor 601 controls the execution. The processor 601 is configured to execute application program code stored in the memory 603 to implement the aspects illustrated 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, PDAs (personal digital assistants), PADs (tablet computers), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. In addition, the electronic device may also be a server, the server may also be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a CDN (Content Delivery Network), and a big data and artificial intelligence platform, but the present application is not limited thereto. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

The embodiment of the present application provides a computer readable storage medium, on which a computer program is stored, and when the computer program runs on a computer, the computer is enabled to execute the corresponding content in the foregoing method embodiment. Compared with the prior art, the performance test method can simulate the online flow to complete the performance test of the load balancing equipment by analyzing the log data of the load balancing equipment during operation, and is beneficial to improving the test accuracy, reducing the test cost and improving the test efficiency.

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless otherwise indicated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the electronic device; or may be separate and not incorporated into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method steps provided by the above-described embodiments.

Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. 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 the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

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 the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). 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 the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present disclosure may be implemented by software or hardware. The name of a module does not in some cases constitute a limitation of the module itself, and for example, the log obtaining module may also be described as a "module for obtaining a log file".

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other combinations of features described above or equivalents thereof without departing from the spirit of the disclosure. For example, the above features and the technical features disclosed in the present disclosure (but not limited to) having similar functions are replaced with each other to form the technical solution.

Claims

1. A method of performance testing, comprising:

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

2. The method of claim 1, wherein parsing the log file for key information related to a user request comprises:

3. The method of claim 2, wherein before filtering each of the log information to obtain key information related to the user request, further comprising:

carrying out validity check on the log information in the log file;

and deleting the log files which do not pass the validity check.

4. The method of claim 3, wherein the checking the validity of the log information in the log file comprises:

5. The method according to claim 3 or 4, wherein the performing the validity check on the log information in the log file comprises:

predicting the abnormal probability that the log information in the log file comprises abnormal information; the abnormality information includes: at least one of preset keywords, variable abnormal information and distribution abnormal information;

6. The method of claim 1, wherein sending a test request to the load balancing device based on the critical information comprises:

7. The method of claim 1, wherein determining the performance of the load balancing device based on the operating status of the load balancing device when processing the test request comprises:

8. The method of claim 7, wherein the running state information comprises at least one of a state file and a kernel dump file; the state file is used for recording information when the running state of the load balancing equipment is normal; the kernel dump file is used for recording information when the running state of the load balancing equipment is abnormal;

determining the operating state of the load balancing device when processing the test request based on whether the operating state information comprises a kernel dump file; if the running state information does not comprise a kernel dump file, determining that the running state of the load balancing equipment is normal; if the running state information comprises a kernel dump file, determining that the running state of the load balancing equipment is abnormal;

and/or determining the running state of the load balancing equipment when the test request is processed based on the ratio of the number of files of the state file to the number of requests of the test request; if the ratio is larger than or equal to a preset ratio, determining that the running state of the load balancing equipment is normal; if the ratio is smaller than a preset ratio, determining that the running state of the load balancing equipment is abnormal;

and/or determining a corresponding standard reaching value of the load balancing equipment when the test request is processed based on the weight coefficients respectively corresponding to the state file and the kernel dump file and the proportion of the number of files in the running state information; if the standard value is smaller than a preset standard threshold value, determining that the running state of the load balancing equipment is abnormal; and if the standard reaching value is larger than or equal to a preset standard reaching threshold value, determining that the running state of the load balancing equipment is normal.

9. A performance testing device, comprising:

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the performance testing method of any of claims 1-8 when executing the program.

11. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which program, when being executed by a processor, carries out the performance testing method of any one of claims 1-8.