Interface pressure testing method, system and device and storage medium

Abstract

The invention is suitable for the technical field of testing, and provides an interface pressure testing method, system and device and a storage medium. According to the test method, a Jmeter test tool is configured for a main control computer and a plurality of load machines based on an agent protocol between the main control computer and the load machines; sending a to-be-tested script to a load machine, wherein the to-be-tested script comprises a plurality of pieces of electrocardiogram data; a Jmeter test tool is called to control a load machine to upload the electrocardiogram data to a target interface according to the uploading priority of the electrocardiogram data so as to carry out pressure test on the target interface; receiving a pressure test result sent by the load machine; according to the embodiment of the invention, the target interface can receive data according to the uploading priority of the electrocardiogram data, the working condition of the target interface when receiving the electrocardiogram data with the uploading priority is tested, and the electrocardiogram data are simultaneously sent to the target interface through a plurality of load machines; and testing the receiving efficiency and the operation stability of the target interface on the electrocardiogram data with the uploading priority under the condition of high pressure.

Description

Technical Field

[0001] The present application belongs to the field of software testing technology, and in particular, relates to an interface pressure testing method, system, device and storage medium. Background Art

[0002] Compared with ordinary electrocardiogram, dynamic electrocardiogram can continuously record up to 100,000 electrocardiogram signals within 24 hours. This can improve the detection rate of non-sustained arrhythmias, especially transient arrhythmias and transient myocardial ischemia, thus expanding the scope of clinical application of electrocardiogram.

[0003] Usually, the analysis methods of dynamic electrocardiogram include signal high-pass and low-pass filtering, signal differential operation, square and integral operation. In the final integral curve, a series of peak points will be found, which may be QSR waves or noise. Then, according to some basic laws of electrocardiogram signals and cardiac electrophysiological activities, the characteristics of each P-QRS-T wave group are found through the calculation of some adaptive thresholds; each heart beat is classified and identified according to each P-QRS-T wave found and the wave groups before and after; on the basis of heart beat classification and identification, various dynamic electrocardiogram analysis results such as arrhythmias and conduction block are generated by analyzing the laws of heart beat changes. Doctors can upload the collected dynamic electrocardiogram data to the dynamic electrocardiogram analysis system to realize the analysis and viewing of electrocardiogram data, which greatly improves the diagnostic efficiency. The dynamic electrocardiogram analysis system built based on the B / S architecture (Brower / Server, browser to server) includes a client, a local area network and a server running the dynamic electrocardiogram analysis system. The doctor logs in to the client to connect to the server running the dynamic electrocardiogram analysis system through the local area network and upload the dynamic electrocardiogram data. The dynamic ECG analysis system supports pre-analysis functions, which can provide timely feedback on some critical ECG data. The existing interface performance test is generally done by the tester first using the Jmeter native tool to edit the test script, and then adjusting the number of concurrency and the number of cycles to perform multiple stress tests, and then record the result data. It cannot support the interface test requirements of priority response. If there are multiple priority response test requirements, it may cause the dynamic ECG analysis system to crash. Therefore, it is urgent to propose an interface stress test method that supports multiple priority responses. Summary of the invention

[0004] In view of this, the embodiments of the present application provide an interface stress testing method, system, device and storage medium to solve the problem that the existing testing method of the dynamic electrocardiogram analysis system cannot support the interface testing requirements of priority response. If there are multiple priority response testing requirements, it may cause the dynamic electrocardiogram analysis system to crash.

[0005] A first aspect of an embodiment of the present application provides an interface pressure testing method, which is applied to a master control machine, wherein the master control machine is connected to a plurality of load machines, and the method comprises:

[0006] Based on the proxy protocol between the master machine and the load machine, configure the Jmeter test tool for the master machine and multiple load machines;

[0007] Sending a script to be tested to a load machine, wherein the script to be tested includes a plurality of ECG data;

[0008] By calling the Jmeter test tool, the load machine is controlled to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface;

[0009] Receive the stress test result sent by the load machine.

[0010] The first aspect of an embodiment of the present application provides an interface stress testing method, which can enable a target interface to receive data according to the upload priority of ECG data, and test the working condition of the target interface when receiving ECG data with upload priority, and send multiple ECG data to the target interface simultaneously through multiple load machines, to test the receiving efficiency and operating stability of the target interface for ECG data with upload priority under high stress conditions.

[0011] A second aspect of an embodiment of the present application provides an interface stress testing system, including a testing platform and a server, wherein the testing platform includes a main control machine and multiple load machines, the main control machine is connected to the multiple load machines respectively, and the server is connected to the multiple load machines respectively through interfaces;

[0012] The main control machine is used for:

[0013] Based on the proxy protocol between the master machine and the load machine, configure the Jmeter test tool for the master machine and multiple load machines;

[0014] Sending a script to be tested to a load machine, wherein the script to be tested includes a plurality of ECG data;

[0015] By calling the Jmeter test tool, the load machine is controlled to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface;

[0016] Receiving the stress test result sent by the load machine;

[0017] The server is used to receive ECG data through a target interface and perform dynamic ECG analysis according to the ECG data.

[0018] A third aspect of an embodiment of the present application provides an interface pressure testing device, comprising:

[0019] Configuration module, used to configure Jmeter test tools for the master machine and multiple load machines based on the proxy protocol between the master machine and the load machine;

[0020] A sending module, used for sending a script to be tested to a load machine, wherein the script to be tested includes a plurality of ECG data;

[0021] A test module, used to control the load machine to upload the ECG data to the target interface according to the upload priority of the ECG data by calling the Jmeter test tool, so as to perform a stress test on the target interface;

[0022] The quantification module is used to receive the stress test result sent by the load machine.

[0023] The fourth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the interface stress testing method provided in the first aspect of the embodiments of the present application are implemented.

[0024] It can be understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0026] Figure 1 is a structural schematic diagram of a test system provided in an embodiment of the present application;

[0027] Figure 2 is an interaction timing diagram of the test system provided in an embodiment of the present application;

[0028] Figure 3 This is a first flow chart of the interface pressure testing method provided in the embodiment of the present application;

[0029] Figure 4 This is a second flow chart of the interface pressure testing method provided in an embodiment of the present application;

[0030] Figure 5 This is a third flow chart of the interface pressure testing method provided in the embodiment of the present application;

[0031] Figure 6This is a first flow chart of the server stress testing method provided in the embodiment of the present application;

[0032] Figure 7 This is a second flow chart of the server stress testing method provided in an embodiment of the present application;

[0033] Figure 8 This is a third flow chart of the server stress testing method provided in the embodiment of the present application;

[0034] Fig. 9 It is a structural schematic diagram of the interface pressure testing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0036] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0037] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0038] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0039] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0040] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0041] In applications, the performance test of existing interfaces is generally done by testers first using the Jmeter native tool to edit the test script, then adjusting the number of concurrency and the number of cycles to perform multiple stress tests, and then recording the result data. It cannot support the interface test requirements of priority response. If there are multiple priority response test requirements, it may cause the dynamic electrocardiograph analysis system to crash. Therefore, it is urgent to propose an interface stress test method that supports multiple priority responses.

[0042] In response to the above technical problems, an embodiment of the present application provides an interface stress testing method, which can enable the target interface to receive data according to the upload priority of the ECG data, and test the working condition of the target interface when receiving ECG data with upload priority, and send multiple ECG data to the target interface at the same time through multiple load machines, to test the target interface's reception efficiency and operating stability for ECG data with upload priority under high stress conditions.

[0043] The interface pressure testing method provided in the embodiment of the present application can be applied to the testing system 100. Figure 1 The schematic diagram of the architecture of the test system 100 is shown as an example. The test system 100 includes a test platform 110 and a server 120. The test platform 110 includes a main control machine 111 and multiple load machines 112. The main control machine 111 is connected to the multiple load machines 112 respectively. The server 120 is connected to the multiple load machines 112 respectively through interfaces.

[0044] The main control machine 111 is used for:

[0045] Based on the proxy protocol between the master machine and the load machine 112, a Jmeter test tool is configured for the master machine and the multiple load machines 112;

[0046] Sending a script to be tested to the load machine 112, wherein the script to be tested includes a plurality of ECG data;

[0047] By calling the Jmeter test tool to control the load machine 112 to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface;

[0048] Receive the stress test result sent by the load machine 112;

[0049] Among them, in this embodiment, the upload priority of the ECG data is determined based on the event identifier of the ECG data;

[0050] The server 120 is used to receive the ECG data through the target interface and perform dynamic ECG analysis according to the ECG data.

[0051] The embodiment of the present application does not impose any limitation on the specific type of the main control machine 111 .

[0052] In the application, the master machine 111 is connected to multiple load machines 112 respectively. The test environment deployed by the master machine 111 and the load machine 112 can be built based on the Jmeter test platform. The test environment of the master machine 111 and the load machine 112 (refer to Figure 1 and Figure 2 ) to illustrate:

[0053] 1. The master machine 111 can store the IP addresses of all load machines 112, and each load machine 112 can store the IP address of the master machine 111, so that when any load machine 112 establishes a connection with the master machine 111, the IP address can be bidirectionally authenticated to improve the security and accuracy of the connection. After completing the bidirectional authentication of the IP address, the master machine 111 can configure the Jmeter test tool for the master machine 111 and each load machine 112 based on the proxy protocol between the master machine 111 and the load machine 112. The IP address stored by the master machine 111 or the load machine 112 can be specifically saved in the remote_hosts configuration file of Jmeter;

[0054] 2. The tester can upload the script to be tested to the main control machine 111, and maintain the script to be tested on the main control machine 111, and can send the script to be tested to each load machine 112 through the main control machine 111; the script to be tested can include multiple ECG data, and the load machine 112 can simulate multiple users to upload ECG data to the server 120 concurrently according to the script to be tested, or the load machine 112 and the main control machine 111 can store ECG data;

[0055] 3. Each load machine 112 establishes a connection with the server 120 through the target interface. The server 120 can return the connection result to the load machine 112, and the load machine 112 can feed back the connection result to the master control machine. The connection between the load machine 112 and the server 120 can be established based on the Websocket protocol (a protocol for full-duplex communication on a single TCP connection), which can support two-way communication between the load machine 112 and the server 120;

[0056] 4. The main control machine 111 can send an upload control instruction to any one or more load machines 112 through the Jmeter test tool. After the load machine 112 starts to execute the upload control instruction, the load machine 112 sends an upload request for ECG data to the server 120. After authorization by the server 120, the load machine 112 can start uploading the ECG data. During the upload, the server 120 can send back the upload progress to the load machine 112, and can also send the stress test result to the load machine 112 after the upload is completed. The load machine 112 feeds back the stress test result to the main control machine 111.

[0057] Figure 2 An interaction sequence diagram of the test system 100 is shown as an example.

[0058] In the application, the device type of the load machine 112 can refer to the device type of the above-mentioned master control machine 111, and will not be repeated here. The multiple load machines 112 included in the test platform 110 can be independent of each other and not connected to each other, and the performances of different load machines can be the same or different. Testers can set up test environments for multiple load machines 112 respectively, or they can connect and control all load machines 112 through a master control device to remotely set up the test environment of all load machines 112 on the master control device side, so that the load machines 112 can perform upload operations according to actual test needs.

[0059] In the application, the server 120 includes at least one communication module and one processing module. The communication module may specifically include multiple interfaces, any of which is used to connect to one or more corresponding load machines 112; the processing module is used to receive the ECG data uploaded by each corresponding load machine 112 through each interface, and can also be used to pre-analyze the ECG data to obtain pre-analysis data. The server 120 may also include a storage module, which may adopt cloud storage and / or local storage storage methods, and the storage module is used to store the above ECG data and pre-analysis data.

[0060] It should be noted that, when performing stress testing, the load machine can upload the ECG data to a target interface connected thereto or to multiple target interfaces connected thereto, and the target interface corresponding to each load machine can be determined by the host control machine.

[0061] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the test system 100. In other embodiments of the present application, the test system 100 may include more or fewer components than those illustrated, or may combine certain components, or may include different components, such as a graphics processing unit (GPU, which may be used to perform GPU accelerated operations on ECG data), etc. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0062] like Figure 3 As shown, the interface stress testing method provided in the embodiment of the present application is applied to the main control machine in the above test system, and performs stress testing on the load capacity of the target interface, including the following steps S301 to S304:

[0063] Step S301: Based on the proxy protocol between the master machine and the load machines, a Jmeter test tool is configured for the master machine and multiple load machines.

[0064] In the application, the master can store the IP addresses of all load machines, and each load machine can store the IP address of the master, so that when any load machine and the master establish a connection, the IP address can be bidirectionally authenticated to improve the security and accuracy of the connection. After completing the bidirectional authentication of the IP address, the master can configure the Jmeter test tool for the master and each load machine based on the proxy protocol between the master and the load machine, so that the master can control the load machine. The IP address stored by the master or the load machine can be specifically saved in the remote_hosts configuration file of Jmeter.

[0065] It should be noted that the embodiment of the present application does not impose any restrictions on the specific type of the proxy protocol between the master machine and the load machine. In addition to the Jmeter test platform, the master machine and the load machine can also build a test environment through test platforms such as RunnerGo and LordRunner. The embodiment of the present application does not impose any restrictions on the specific type of the test platform.

[0066] Step S302: sending the script to be tested to the load machine, where the script to be tested includes a plurality of ECG data.

[0067] In the application, testers can upload the script to be tested to the main control machine and maintain the script on the main control machine. The script to be tested can be sent to each load machine through the main control machine. The script to be tested can include multiple ECG data, and the load machine can simulate a scenario in which a large amount of ECG data is uploaded to the server concurrently based on the script to be tested.

[0068] In one embodiment, the script to be tested may not include ECG data, and the load machine may store ECG data locally.

[0069] Step S303, by calling the Jmeter test tool to control the load machine to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface;

[0070] The upload priority of the ECG data is determined based on the event identifier of the ECG data.

[0071] In the application, the upload priority of the ECG data is determined based on the event identifier of the ECG data. The event identifier of the ECG data can be used for abnormal conditions in the ECG data. When the ECG data has an event identifier, the corresponding ECG data upload priority can be given, thereby meeting the test requirement that ECG data with abnormal conditions needs to be responded to first.

[0072] In the application, by configuring the upload priority for ECG data, it can be uploaded to the server with higher priority than ECG data without abnormal conditions, so that doctors can know the patient's abnormal ECG data at the first time, thereby speeding up the discovery of potential or existing diseases.

[0073] In the application, the upload priority may include only one level or multiple levels (for example, a first upload priority, a second upload priority and a third priority). Specifically, when the upload priority includes multiple levels, a comparison table of time identifiers and upload priority levels may be pre-set, so that the upload priority may be quickly determined by looking up the table after obtaining the event identifier.

[0074] Furthermore, the event identifier of the ECG data can be determined based on the critical feature information of the ECG data, or the event identifier is determined based on the critical template matched by the ECG data. Specifically, the ECG data can contain a variety of indicators, and whether the ECG data has critical feature information can be determined based on whether the target indicator exceeds the corresponding preset indicator threshold. The target indicators may include the ventricular rate of supraventricular tachycardia, the ventricular rate of supraventricular tachycardia and the corresponding duration, the shortest RR interval of atrial fibrillation accompanied by ventricular preexcitation (RR interval is the interval time between each heart beat), the average ventricular rate or the time of symptoms accompanied by a long RR interval, etc.

[0075] For example, assuming that the first preset indicator threshold value of the ventricular rate of supraventricular tachycardia is 200bpm, if the ventricular rate of supraventricular tachycardia is 250bpm, it is determined that the corresponding ECG data has critical feature information corresponding to the ventricular rate of supraventricular tachycardia; assuming that the second preset indicator threshold value of the ventricular rate of supraventricular tachycardia is 150bpm, and the third preset indicator threshold value of the corresponding duration is 30s, if the ventricular rate of supraventricular tachycardia is 170bpm and the duration is 35s, it is determined that the corresponding ECG data has critical feature information corresponding to the ventricular rate of supraventricular tachycardia and the corresponding duration; assuming that the fourth preset indicator threshold value of the time of symptoms associated with a long RR interval is 3s, if the time of symptoms associated with a long RR interval is 2.5s, it is determined that the corresponding ECG data does not have critical feature information corresponding to the ventricular rate of supraventricular tachycardia.

[0076] In the application, multiple emergency templates can be preset. The emergency templates are used to indicate abnormal waveforms of ECG data. For example, they can be abnormal waveforms used to reflect symptoms such as sinus tachycardia, sinus bradycardia, atrial arrhythmia or ventricular arrhythmia, or abnormal waveforms such as ST segment elevation, QRS wave widening, P wave widening, T wave inversion, etc. By comparing the ECG data with each emergency template, it can be determined whether the ECG data has a matching emergency template.

[0077] In one embodiment, before step S303, the method further includes:

[0078] Quantify the computing power resources of the load machine by calling the Jmeter test tool, and determine the number of concurrent data based on the computing power resources of the load machine;

[0079] Step S303 includes:

[0080] By calling the Jmeter test tool to control the load machine to upload the ECG data to the target interface according to the upload priority and concurrent data quantity of the ECG data, the target interface is stress tested.

[0081] In the application, the Jmeter test tool deployed on each load machine can quantify the computing resources of the load machine and determine the number of concurrent data based on the computing resources of the load machine, so that the ECG data can be uploaded to the target interface according to the upload priority and concurrent number of ECG data to perform stress testing on the target interface. As much data as possible can be uploaded to the target interface concurrently at the same time, and the computing resources of the load machine can be fully utilized to reduce resource waste.

[0082] It should be noted that when the concurrent number of data on the load machine is less than the ECG data with upload priority, the ECG data with upload priority will be uploaded first until the concurrent number of data is greater than the ECG data with upload priority; when the concurrent number of data on the load machine is greater than the ECG data with upload priority, while all ECG data with upload priority are being uploaded concurrently, ECG data without upload priority are randomly selected for concurrent upload to meet the concurrent number of data.

[0083] Step S304: receiving the stress test result sent by the load machine.

[0084] In the application, after the load machine completes the upload of ECG data, it can obtain the stress test results of the load machine on the target interface during the test process, and each load machine can send the stress test results to the main control machine. Among them, the stress test results can be that when the server receives ECG data through the target interface, it monitors the working conditions of the local components of the server and the reception of ECG data, so as to obtain the full-cycle performance of the target interface when receiving ECG data. Specifically, the performance of the target interface can include the performance indicators and average reception time of the target component receiving ECG data, wherein the performance indicators of the target component can include processor indicators and average reception time, and the processor indicators can specifically include the occupancy rate of the thread used to execute the reception of ECG data in the processor; the average reception time represents the average time of receiving ECG data of each load machine. The reception of ECG data can include the reception order of each ECG data of the target interface and the amount of load data of the target interface, and the amount of load data can reflect the amount and amount change of ECG data borne by the target interface when receiving ECG data.

[0085] In the application, the main control machine can determine whether the target interface receives data according to the upload priority of the ECG data based on the order in which the target interface receives each ECG data. At the same time, combined with the amount of load data, the load situation of the target interface can be quantified, so that when the target interface is under high pressure, the reception efficiency of the target interface for the ECG data with upload priority can be obtained.

[0086] In one embodiment, step S304 includes:

[0087] By calling the Jmeter test tool:

[0088] The control server generates sub-stress test results and sends the sub-stress test results to the corresponding load machine; each sub-stress test result is determined based on the performance of the target interface when the corresponding load machine uploads the ECG data;

[0089] Receive the sub-stress test results sent by each load machine, and obtain the global stress test results according to the sub-stress test results sent by each load machine.

[0090] In the application, the server can generate a sub-stress test report for the ECG data uploaded by each load machine, and send the sub-stress test report to the corresponding load machine. The load machine then sends the sub-stress test report to the main control machine, so that the main control machine can obtain the global stress test results based on the sub-stress test results, which is convenient for the main control machine to perform stress test analysis on the target interface.

[0091] In the application, the Jmeter test tool is configured for the master machine and multiple load machines based on the proxy protocol between the master machine and the load machine; the script to be tested is sent to the load machine, and the script to be tested includes multiple ECG data; the load machine is controlled by calling the Jmeter test tool to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface; the stress test result sent by the load machine is received; the target interface can be controlled to receive data according to the upload priority of the ECG data, and the working condition of the target interface when receiving the ECG data with the upload priority is tested, and multiple ECG data are sent to the target interface at the same time through multiple load machines, so as to test the receiving efficiency and operation stability of the target interface for the ECG data with the upload priority under high pressure.

[0092] like Figure 4 As shown, in one embodiment, based on Figure 3 The corresponding embodiment includes the following steps S401 to S405:

[0093] Step S401: Based on the proxy protocol between the master machine and the load machine, configure the Jmeter test tool for the master machine and multiple load machines;

[0094] Step S402: sending the script to be tested to the load machine, where the script to be tested includes a plurality of ECG data.

[0095] In the application, the interface pressure testing method provided in step S401 and step S402 can refer to the relevant description in the above step S301 and step S302, which will not be repeated here.

[0096] Step S403: calling the Jmeter test tool to control the load machine to determine the upload priority of the corresponding ECG data based on the event identifier of the ECG data.

[0097] In the application, the Jmeter test tool can be called to control the load machine to execute the script to be tested, thereby controlling the load machine to determine the upload priority of the corresponding ECG data based on the event identifier of the ECG data. The following describes the method for obtaining the event identifier:

[0098] 1. The script to be tested includes at least one event identifier of the ECG data, that is, the script to be tested can carry the event identifier of the ECG data. In the actual ECG dynamic analysis system, the user can obtain a dynamic ECG by wearing an acquisition device. The acquisition device can have the ability to recognize event identifiers, that is, the ability to recognize the critical feature information of the ECG data or the ability to judge whether the ECG data matches the critical template.

[0099] 2. By calling the Jmeter test tool to control the load machine to analyze the ECG data and obtain the event identifier of the ECG data, the load machine can have the ability to analyze the ECG data locally, so that the event identifier of the ECG data can be identified locally on the load machine;

[0100] 3. By calling the Jmeter test tool: control the load machine to send ECG data to the target interface; control the server to receive ECG data through the target interface, and analyze the ECG data to obtain the event identifier of the ECG data; control the server to feedback the event identifier of the ECG data to the load machine through the target interface; the load machine can send the ECG data to the target interface, and identify the event identifier of the ECG data through the server, and feedback the event identifier of the ECG data to the load machine. It should be noted that when the load machine sends the ECG data to the target interface for event identifier identification, it can only send some or all indicators in the ECG data, thereby reducing the amount of data transmission and reducing the resource usage for event identifier identification.

[0101] Step S404, by calling the Jmeter test tool to control the load machine to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface;

[0102] Step S405: receiving the stress test result sent by the load machine.

[0103] In the application, the interface pressure testing method provided in step S404 and step S405 can refer to the relevant description in the above step S303 and step S304, which will not be repeated here.

[0104] In the application, by using ECG data with event identifiers for testing and using a load machine to identify the event identifiers in real time, the authenticity of the test on the target interface can be improved to simulate the situation in which ECG data with and without event identifiers are uploaded to the target interface concurrently in an actual scenario.

[0105] like Figure 5 As shown, in one embodiment, based on Figure 4 The corresponding embodiment includes the following steps S501 to S505:

[0106] Step S501: Based on the proxy protocol between the master machine and the load machine, configure the Jmeter test tool for the master machine and multiple load machines;

[0107] Step S502: Send the script to be tested to the load machine, where the script to be tested includes a plurality of ECG data.

[0108] In the application, the interface pressure testing method provided by step S501 and step S502 can refer to the relevant description in the above step S301 and step S302, which will not be repeated here.

[0109] Step S503: calling the Jmeter test tool to control the load machine to determine the upload priority of the corresponding ECG data based on the event identifier of the ECG data.

[0110] Step S504: Determine multiple target load machines participating in the test according to the thread configuration parameters.

[0111] In the application, the script to be tested may also include thread configuration parameters, which can be used to determine one or more target load machines involved in the test, so that the load machine resources can be flexibly called to adjust the test pressure of the target interface. The number of load machine calls is positively correlated with the test pressure of the target interface. The master control machine can also adjust the number of concurrent data of the corresponding target load machine according to the real-time load of each target load machine to give full play to the performance of the test platform and effectively test the limit performance of the target interface. (For details, please refer to the relevant description in step S803 below)

[0112] Step S505, by calling the Jmeter test tool to control the target load machine to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface;

[0113] Step S506: receiving the stress test result sent by the load machine.

[0114] In the application, the interface pressure testing method provided in step S504 and step S505 can refer to the relevant description in the above step S303 and step S304, which will not be repeated here.

[0115] like Figure 6 As shown, the server stress testing method provided in the embodiment of the present application is applied to the above-mentioned test system (see Figure 1 ), a stress test is performed on the load capacity of the server, including the following steps S601 and S602:

[0116] Step S601: for any load machine, the load machine performs an upload operation based on the upload control instruction to simulate multiple users concurrently uploading ECG data to the server; wherein, when at least two load machines are controlled to perform the upload operation by the upload control instruction, the upload control instruction is used to control at least two load machines to perform the upload operation simultaneously.

[0117] In the application, the working principle of the load machine is explained below by taking any load machine included in the test platform as an example. The working principles of other load machines can refer to the working principles of any of the above load machines. The load machine can receive upload control instructions. The upload control instructions can be created by the tester locally on the load machine, or the upload control instructions can be received by connecting to an external device. The external device can be a removable storage device, or the upload control instructions can be received by connecting to a main control device. The load machine performs an upload operation by responding to the upload control instruction to simulate multiple users uploading ECG data to the server concurrently, wherein the upload control instruction can be used to configure the start time and the number of concurrent data for executing the upload operation. The ECG data can be the ECG data stored locally on the load machine, or the ECG data carried by the upload control instruction.

[0118] In the application, the upload control instruction can control multiple load machines to perform upload operations. Specifically, when the upload control instruction is used to control at least two load machines to perform the upload operation, the upload control instruction is used to control the at least two load machines to perform the upload operation at the same time. Specifically, the upload control instruction can be used to configure the start time of the at least two load machines to perform the upload operation to be the same time; or, the upload control instruction can be sent to the at least two load machines at the same time, and the at least two load machines can perform the upload operation immediately when receiving the upload control instruction.

[0119] Step S602: quantify the load capacity of the server according to the first performance of the server when receiving the ECG data and the number of load users of the server.

[0120] In the application, the server can obtain the first performance of the whole cycle of receiving ECG data by monitoring the working conditions of the local components and the reception of ECG data. Specifically, the first performance can include the performance index and average reception time of the target component of the device receiving ECG data, wherein the performance index of the target component can include the processor index and the average reception time, and the processor index can specifically include the utilization rate of the processor, the occupancy rate of the thread used to execute the reception of ECG data in the processor, and the frequency of the processor; the average reception time represents the average time of receiving the ECG data of each user.

[0121] In the application, the number of load users can reflect the change in the number of users participating in uploading ECG data when the server receives ECG data. Combining the first performance and the number of load users, the number of load users corresponding to the server under different performances can be known to quantify the load capacity of the server. Specifically, the load capacity curve of the server can be fitted according to the number of load users corresponding to the server under different performances, or a load capacity comparison table corresponding to the performance and the number of load users can be established. The embodiment of the present application does not impose any restrictions on the method for quantifying the load capacity of the server.

[0122] In the application, after obtaining the quantitative results of the server's load capacity, the system performance can be allocated according to the number of load users, or the number of load users can be controlled according to the system performance, to achieve flexible deployment of system performance and flexible adjustment of the number of load users, and when the number of load users reaches the upper limit of the number of load users, or when the system performance reaches the upper limit of the system performance, the number of load users can be limited, so as to avoid system overload while giving full play to the system performance and improve the operating stability of the dynamic ECG analysis system.

[0123] In one embodiment, step S602 further includes:

[0124] The server is used to determine the receiving priority based on the critical feature information of the electrocardiogram data.

[0125] In the application, the server may also include a sorting sequence number module, which is used to determine the sorting sequence number of the ECG data when the ECG data is sent to the server. The server can read and store each ECG data in sequence according to the sorting sequence number of each ECG data, and the sorting sequence number of the ECG data can be determined according to the time when the ECG data arrives at the server. The sorting sequence number module can also have a function of judging the receiving priority. Specifically, when the ECG data is sent to the server, the event identifier of the ECG data is obtained, and the receiving priority of the corresponding ECG data is determined according to the event identifier of the ECG data. If the sorting sequence number module enables the judging function of the receiving priority, the sorting sequence number of the ECG data can be determined according to the time when the ECG data arrives at the server and the receiving priority of the corresponding ECG data. The sorting sequence numbers of the receiving priority level from high to low can include the first receiving priority, the second receiving priority and the third receiving priority, etc. When the time when the ECG data arrives at the server is the same, the higher the level of the receiving priority, the smaller the sorting sequence number, that is, the higher the sorting priority. For example, assuming that ECG data a and ECG data b arrive at the server at the same time, ECG data a has the first receiving priority, and ECG data b has the third receiving priority, then the sorting number of ECG data a is smaller than the sorting number of ECG data b.

[0126] In the application, the event identifier of the ECG data can be determined based on the critical feature information of the ECG data, or the event identifier can be determined based on the critical template matched by the ECG data. The specific determination method can refer to the relevant description in the above step S303, which will not be repeated here.

[0127] In one embodiment, step S602 further includes:

[0128] The server is used to perform pre-analysis on the ECG data when receiving the ECG data to obtain analysis results of the corresponding ECG data.

[0129] In the application, the server can perform pre-analysis on the ECG data when receiving the ECG data to obtain the pre-analyzed ECG data. Specifically, the pre-analysis may include at least one stage of pre-analysis, which may include a first stage pre-analysis and a second stage pre-analysis. The first stage pre-analysis may perform heart beat detection, heart beat classification, ST point feature point calculation, and QT point feature point calculation on the ECG data; the second stage pre-analysis may be implemented by a preset algorithm, which is pre-stored in the server. The preset algorithm may include an arrhythmia judgment algorithm, an atrial flutter / atrial fibrillation detection algorithm, an HRV (Heart Rate Variability) analysis algorithm, an ST event detection algorithm, an ST trend calculation algorithm, a QT trend calculation algorithm, a sleep apnea analysis algorithm, an HRT (Heart Rate Turbulence) analysis, and a T wave alternans analysis.

[0130] In the application, the first stage pre-analysis can adjust the specific settings of the first stage pre-analysis by configuring the first pre-analysis parameters. The first pre-analysis parameters can be used to determine the switch state of PACE (Pacing and Clinical Electrophysiology), the type of PACE, and the location of PACE. The second stage pre-analysis can configure the permission parameters and configuration parameters to determine the corresponding user's permission to use the preset algorithm. The permission parameters can be stored locally on the server or passed in by the user client (in the test method through the load machine); the configuration parameters are used to fine-tune the corresponding preset algorithm. The configuration parameters can be set by the user and sent to the server through the load machine. For example, assuming that the preset algorithm includes an HRV analysis algorithm, the corresponding configuration parameters may include a maximum RR interval threshold and a minimum RR interval threshold; assuming that the preset algorithm includes an ST event detection algorithm, the corresponding configuration parameters may be an ST elevation threshold and an ST depression threshold.

[0131] In the application, after the pre-analysis of the ECG data is completed, the analysis results of the corresponding ECG data can be obtained and stored locally on the server, so that doctors can quickly call the corresponding analysis results when reading the ECG data, thereby improving the doctor's diagnostic efficiency.

[0132] In the application, an upload operation is performed by a load machine based on an upload control instruction to simulate multiple users concurrently uploading ECG data to a server; wherein, when at least two load machines are controlled to perform an upload operation by the upload control instruction, the upload control instruction is used to control at least two load machines to perform the upload operation simultaneously; the load capacity of the server is quantified according to the first performance of the server when receiving the ECG data and the number of load users of the server, and by controlling multiple load machines to simultaneously simulate the operation of multiple users concurrently uploading ECG data, the high load of the server in a high-concurrency scenario can be simulated, and the load capacity / number of load users corresponding to the server under different performance performances can be obtained, which is beneficial to manage the user flow of the system according to the load capacity of the server after the ECG analysis system is put into use, and can avoid system overload while giving full play to the system performance, thereby improving the operating stability of the dynamic ECG analysis system.

[0133] like Figure 7 As shown, in one embodiment, based on Figure 6 The corresponding embodiment includes the following steps S701 to S703:

[0134] Step S701, sending an upload control instruction to at least one load machine through the host machine; the upload control instruction carries a script to be tested, and the load machine is used to simulate multiple users to concurrently upload ECG data to the server according to the script to be tested;

[0135] Step S702: for any load machine, the load machine performs an upload operation based on the upload control instruction to simulate multiple users uploading ECG data to the server concurrently; wherein, when at least two load machines are controlled to perform the upload operation by the upload control instruction, the upload control instruction is used to control at least two load machines to perform the upload operation simultaneously;

[0136] Step S703: quantify the load capacity of the server according to the first performance of the server when receiving the ECG data and the number of load users of the server.

[0137] In the application, the working principle of the host sending upload control instructions can refer to the above Figure 1 The relevant descriptions in the corresponding embodiments are not repeated here. The test method provided by step S702 can refer to the test method provided by the above step S601, which is not repeated here. The following is an explanation of the quantification method of the load capacity of the server when the test platform includes a host control machine:

[0138] In one embodiment, step S703 includes:

[0139] When the server receives ECG data, for a group of ECG data uploaded by any load machine, the server records the sub-load test results of receiving a group of ECG data, and sends the sub-load test results of each group of ECG data to each corresponding load machine; the sub-load test results are determined according to the local performance of the server when receiving the corresponding group of ECG data, and the number of users of the server bearing the load of the corresponding load machine;

[0140] The master machine receives the sub-load test results sent by each load machine, and summarizes the sub-load test results of all load machines to obtain the global load test result to quantify the load capacity of the server.

[0141] In the application, when the test platform includes a main control machine, the test data of the server can be collected through the main control machine to quantify the load capacity of the server and feed it back to the tester. Specifically, when the server receives the ECG data, it can distinguish the groups of ECG data uploaded by each load machine, and can independently record the sub-load test results when receiving each group of ECG data. After completing the reception of the ECG data, the sub-load test results of each group of ECG data can be sent to each corresponding load machine, and the sub-load test results sent by each load machine can be received through the main control machine, so that the main control machine can summarize the global load test results, which is convenient for testers to collect and analyze test data on the main control machine, and can effectively trace the transmission errors of the sub-load test results and lock the load machine corresponding to the abnormal sub-load test results.

[0142] In the application, the sub-load test results may include the average receiving time, median receiving time, minimum receiving time, maximum receiving time, receiving time when the receiving progress reaches the preset receiving progress (e.g. 50%, 70%, 90%, etc.), query speed per second, data volume received per second, data throughput and receiving error rate when the server receives the corresponding set of ECG data. After obtaining the global load test results, the main control machine can process the global load test results through the preset analysis script and generate an aggregate report, which is helpful for testers to quickly understand the test situation.

[0143] In the application, the upload control instructions are managed and maintained by the main control machine, and the main control machine controls multiple load machines at the same time, which can improve the consistency and maintainability of the upload control instructions, thereby improving the efficiency and stability of concurrent testing and reducing the management cost of the test platform.

[0144] like Figure 8 As shown, in one embodiment, based on Figure 6 The corresponding embodiment includes the following steps S801 to S804:

[0145] Step S801, sending an upload control instruction to at least one load machine through the host machine; the upload control instruction carries the script to be tested, and the load machine is used for the script to be tested to simulate multiple users to concurrently upload ECG data to the server;

[0146] Step S802: for any load machine, the load machine performs an upload operation based on the upload control instruction to simulate multiple users concurrently uploading ECG data to the server; wherein, when at least two load machines are controlled to perform the upload operation by the upload control instruction, the upload control instruction is used to control at least two load machines to perform the upload operation simultaneously.

[0147] In the application, the test methods provided in step S801 and step S802 may refer to the test methods provided in the above-mentioned step S701 and step S702, and will not be described in detail here.

[0148] Step S803: When any load machine performs an upload operation, the host control machine dynamically adjusts the data concurrency quantity of the load machine based on the second performance of the load machine.

[0149] In the application, the master machine can also monitor the second performance of each load machine and dynamically adjust the number of concurrent load machines based on the second performance index of the load machine. Specifically:

[0150] When any load machine performs an upload operation, the second performance of the load machine is obtained through the master control machine;

[0151] If the second performance of the load machine does not reach the second preset performance range, increase the number of concurrent data of the load machine until the performance reaches the second preset performance range;

[0152] If the second performance of the load machine is within the second preset performance range, the data concurrency quantity of the load machine is maintained.

[0153] In the application, the second performance of the load machine may include performance indicators of the target element of the load machine, wherein the performance indicators of the target element may include processor indicators, and the processor indicators may specifically include processor utilization, occupancy of the thread used to execute uploading ECG data in the processor, and processor frequency.

[0154] For example, assuming that the processor indicator includes the processor utilization, the second preset performance range is that the processor utilization is between [95%, 98%], if the second performance of the load machine is that the processor utilization is 90% and the number of concurrent data is 4, then the second preset performance range is not reached, and the number of concurrent data can be increased to 5; the processor utilization is obtained again, if the processor utilization is 94%, the number of concurrent data can be increased to 6; the processor utilization is obtained again, if the processor utilization is 97%, the number of concurrent data of the load machine is maintained.

[0155] It should be noted that if the second performance exceeds the second preset performance range, the number of concurrent data of the load machine can be reduced to avoid failure caused by overload of the load machine.

[0156] Step S804: The server obtains the first performance when receiving the ECG data, and dynamically adjusts the number of load users of the server to quantify the load capacity of the server.

[0157] In one embodiment, step S804 includes:

[0158] The first performance when receiving ECG data through the server;

[0159] If the first performance of the server does not reach the first preset performance range, increase the number of load users of the server until the first performance reaches the first preset performance range;

[0160] If the first performance of the server is within a first preset performance range, the number of loaded users of the server is maintained.

[0161] In the application, the method for dynamically adjusting the number of load users by the server can refer to the method for adjusting the number of concurrent data by the load machine. The difference is that the first performance of the server includes the performance indicators and average receiving time of the processor, and the number of load users of the server can be adjusted only according to the performance indicators of the processor to improve the performance control effect of the server; the adjustment of the number of concurrent data by the load machine is controlled by the main control machine, and the adjustment of the number of load users by the server is controlled by the server itself.

[0162] It should be noted that when the adjustment of the data concurrency number of the load machine conflicts with the adjustment of the load user number of the server, for example, when the load machine increases the data concurrency number and the server reduces the load user number or the load user number of the server remains unchanged, the server receives ECG data strictly according to the load user number. At this time, the load machine can reduce the data concurrency number, or the load machine can temporarily idle redundant upload threads until the load user number of the server is greater than or equal to the data concurrency number of all load machines.

[0163] In the application, the main control machine adjusts the number of concurrent data according to the second performance of the load machine, so as to give full play to the performance of the load machine and increase the number of concurrent data as much as possible, thereby increasing the test pressure of multi-user concurrent scenarios and effectively testing the extreme performance of the server; and the server adjusts the number of load users according to the local first performance, so as to fully squeeze the load capacity of the server to test the extreme performance of the server.

[0164] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0165] like Fig. 9 As shown, the embodiment of the present application also provides an interface pressure test device for executing the steps in the above interface pressure test embodiment. The interface pressure device can be a virtual appliance in the terminal device, which is run by the processor of the terminal device, or it can be the terminal device itself.

[0166] like Fig. 9 As shown, the interface pressure testing device 200 provided in the embodiment of the present application includes:

[0167] Configuration module 210, used for configuring Jmeter test tool for the master machine and multiple load machines based on the proxy protocol between the master machine and the load machines;

[0168] The sending module 220 is used to send the script to be tested to the load machine, where the script to be tested includes a plurality of ECG data;

[0169] The test module 230 is used to control the load machine to upload the ECG data to the target interface according to the upload priority of the ECG data by calling the Jmeter test tool, so as to perform a stress test on the target interface;

[0170] The quantification module 240 is used to receive the stress test result sent by the load machine;

[0171] The upload priority of the ECG data is determined based on the event identifier of the ECG data.

[0172] In application, each module in the concurrent performance testing device 200 may be a software program module, or may be implemented by different logic circuits integrated in a processor, or may be implemented by multiple distributed processors.

[0173] In one embodiment, the interface pressure testing device 200 further includes:

[0174] The upload priority determination module is used to control the load machine to determine the upload priority of the corresponding ECG data based on the event identifier of the ECG data by calling the Jmeter test tool.

[0175] In one embodiment, the interface pressure testing device 200 further includes:

[0176] A thread configuration module is used to determine multiple target load machines participating in the test according to thread configuration parameters;

[0177] The test module 230 includes:

[0178] The first sub-test unit is used to control the target load machine to upload the ECG data to the target interface according to the upload priority of the ECG data by calling the Jmeter test tool, so as to perform a stress test on the target interface;

[0179] When at least two target load machines are controlled simultaneously by the Jmeter test tool to perform stress testing on the target interface, at least two target load machines are controlled to simultaneously perform an operation of uploading the ECG data.

[0180] In one embodiment, the interface pressure testing device 200 further includes:

[0181] The concurrent quantity configuration module is used to quantify the computing power resources of the load machine by calling the Jmeter test tool, and determine the concurrent quantity of data according to the computing power resources of the load machine;

[0182] The test module 230 includes:

[0183] The second sub-test unit controls the load machine by calling the Jmeter test tool to upload the ECG data to the target interface according to the upload priority and concurrent data quantity of the ECG data, so as to perform stress testing on the target interface.

[0184] In one embodiment, the quantization module 240 includes:

[0185] Aggregate the quantitative units used by calling the Jmeter test tool:

[0186] The control server generates sub-stress test results and sends the sub-stress test results to the corresponding load machine; each sub-stress test result is determined based on the performance of the target interface when the corresponding load machine uploads the ECG data;

[0187] Receive the sub-stress test results sent by each load machine, and obtain the global stress test results according to the sub-stress test results sent by each load machine.

[0188] It should be noted that the information interaction, execution process and other contents between the above-mentioned modules are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0189] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned function allocation can be completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The functional modules in the embodiment can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. In addition, the specific names of the functional modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the modules in the above-mentioned system can refer to the corresponding process in the above-mentioned method embodiment, which will not be repeated here.

[0190] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the steps in the above-mentioned various interface stress testing method or server stress testing method embodiments.

[0191] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may at least include: any entity or device that can carry the computer program code to the camera terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a disk or an optical disk.

[0192] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0193] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0194] In the embodiments provided in the present application, it should be understood that the disclosed terminal device and method can be implemented in other ways. For example, the terminal device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0195] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. An interface pressure testing method, characterized in that: Applied to a master control machine, the master control machine is connected to a plurality of load machines, the method comprises: Based on the proxy protocol between the master machine and the load machine, configure the Jmeter test tool for the master machine and multiple load machines; Sending a script to be tested to a load machine, wherein the script to be tested includes a plurality of ECG data; By calling the Jmeter test tool, the load machine is controlled to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface; Receive the stress test result sent by the load machine.

2. The interface pressure testing method according to claim 1, characterized in that: The method further comprises: Parsing the ECG data to obtain event identifiers of the ECG data; Determining the uploading priority of the ECG data according to the event identifier of the ECG data; Among them, calling the Jmeter test tool to control the load machine according to the upload priority of the ECG data includes: The Jmeter test tool is called to control the load machine to determine the upload priority of the ECG data based on the event identifier of the ECG data.

3. The interface pressure testing method according to claim 2, characterized in that: The load machine is connected to the server via a target interface, and the server is used to obtain an event identifier of the electrocardiogram data according to the electrocardiogram data. The method further includes: By calling the Jmeter test tool: Controlling the load machine to send the ECG data to the target interface; The control server receives the ECG data through the target interface, and analyzes the ECG data to obtain an event identifier of the ECG data; The server is controlled to feed back the event identifier of the electrocardiogram data to the load machine through the target interface.

4. The interface pressure testing method according to claim 1, characterized in that: The script to be tested also includes thread configuration parameters, and the method further includes: Determine multiple target load machines participating in the test based on thread configuration parameters; The method of calling the Jmeter test tool to control the load machine to upload the ECG data to the target interface according to the upload priority of the ECG data to perform a stress test on the target interface includes: By calling the Jmeter test tool, the target load machine is controlled to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface; When at least two target load machines are controlled simultaneously by the Jmeter test tool to perform stress testing on the target interface, the at least two target load machines are controlled to simultaneously perform an operation of uploading the ECG data.

5. The interface pressure testing method according to claim 1, characterized in that: The method further comprises: Quantify the computing power resources of the load machine by calling the Jmeter test tool, and determine the number of concurrent data according to the computing power resources of the load machine; The method of calling the Jmeter test tool to control the load machine to upload the ECG data to the target interface according to the upload priority of the ECG data to perform a stress test on the target interface includes: By calling the Jmeter test tool, the load machine is controlled to upload the ECG data to the target interface according to the upload priority and concurrent data quantity of the ECG data, so as to perform a stress test on the target interface.

6. The interface pressure testing method according to claim 1, characterized in that: The load machine is connected to the server via a target interface, and the server is used to perform dynamic electrocardiogram analysis according to the electrocardiogram data. The receiving of the stress test result sent by the load machine includes: By calling the Jmeter test tool: Controlling the server to generate sub-stress test results, and sending the sub-stress test results to the corresponding load machine; each sub-stress test result is determined based on the performance of the target interface when a corresponding load machine uploads ECG data; Receive the sub-stress test results sent by each load machine, and obtain the global stress test results according to the sub-stress test results sent by each load machine.

7. The interface pressure testing method according to any one of claims 1 to 6, characterized in that: The event identifier is determined based on critical feature information of the electrocardiogram data, or the event identifier is determined based on a critical template matched by the electrocardiogram data.

8. An interface pressure testing system, characterized in that: The test platform comprises a main control machine and a plurality of load machines, the main control machine is connected to the plurality of load machines respectively, and the server is connected to the plurality of load machines respectively through interfaces; The main control machine is used for: Based on the proxy protocol between the master machine and the load machine, configure the Jmeter test tool for the master machine and multiple load machines; Sending a script to be tested to a load machine, wherein the script to be tested includes a plurality of ECG data; By calling the Jmeter test tool, the load machine is controlled to upload the ECG data to the target interface according to the upload priority of the ECG data, so as to perform a stress test on the target interface; Receiving the stress test result sent by the load machine; The server is used to receive ECG data through a target interface and perform dynamic ECG analysis according to the ECG data.

9. An interface pressure testing device, characterized in that: include: Configuration module, used to configure Jmeter test tools for the master machine and multiple load machines based on the proxy protocol between the master machine and the load machine; A sending module, used for sending a script to be tested to a load machine, wherein the script to be tested includes a plurality of ECG data; A test module, used to control the load machine to upload the ECG data to the target interface according to the upload priority of the ECG data by calling the Jmeter test tool, so as to perform a stress test on the target interface; The quantification module is used to receive the stress test result sent by the load machine.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the interface pressure testing method according to any one of claims 1 to 7 are implemented.

Images