Model stress test performance determination method and device, server and storage medium

Abstract

The present application relates to the technical field of big data intelligent analysis, and in particular to a method and device, server and storage medium for determining model stress testing performance. A method for determining model stress testing performance, comprising: obtaining a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface; executing the first use case and obtaining a first data set corresponding to the first use case; importing the first data set into a second data set corresponding to the second use case, and executing the second use case; the second use case starts executing no earlier than the first use case starts executing; obtaining a first execution result of the first use case and a second execution result of the second use case, and determining the stress testing performance of the non-funnel model based on the first execution result and the second execution result. The present application can improve the accuracy of determining the model stress testing performance of the non-funnel model.

Description

Technical Field

[0001] The present application relates to the technical field of big data intelligent analysis, and in particular to a method and device for determining model stress testing performance, a server, and a storage medium. Background Art

[0002] With the development of economy and technology, the pace of life and work intensity have increased. For the convenience of users, various applications have been created. After the application is released, the model used by the server needs to withstand a certain amount of pressure so that it can provide corresponding services when the number of users using the application reaches a certain level. Therefore, determining the performance of the model through stress testing has become the focus of users. Summary of the invention

[0003] The present application provides a method and device for determining model stress testing performance, a server and a storage medium, the main purpose of which is to improve the accuracy of determining the model stress testing performance of a non-funnel model.

[0004] According to one aspect of the present application, a method for determining model stress testing performance is provided, comprising:

[0005] Acquire a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface;

[0006] Execute the first use case and obtain a first data set corresponding to the first use case;

[0007] Importing the first data set into a second data set corresponding to the second use case, and executing the second use case;

[0008] The execution time of the second use case starts no earlier than the execution time of the first use case starts;

[0009] A first execution result of the first use case and a second execution result of the second use case are obtained, and based on the first execution result and the second execution result, a stress testing performance of the non-funnel model is determined.

[0010] Optionally, importing the first data set into a second data set corresponding to the second use case includes:

[0011] Obtaining execution data corresponding to the first data set;

[0012] If the execution data satisfies a first execution condition, the first data set is imported into a second data set corresponding to the second use case.

[0013] Optionally, the execution data is execution duration, and if the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case includes:

[0014] Obtaining the execution time of the first use case;

[0015] Determining a duration threshold corresponding to the execution duration based on a first request amount corresponding to the first use case and a second request amount corresponding to the second use case, wherein the first request amount is less than the second request amount;

[0016] If the execution time reaches the time threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0017] Optionally, executing the second use case includes:

[0018] If the execution time reaches the time threshold, the second use case starts to be executed.

[0019] Optionally, the execution data is a data volume, and if the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case includes:

[0020] Obtaining the data volume corresponding to the first data set;

[0021] If the data volume reaches the data volume threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0022] Optionally, if the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case includes:

[0023] If the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case, resetting the execution data and reacquiring the first data set;

[0024] If the re-acquired execution data meets the second execution condition, the re-acquired first data set is imported into the second data set corresponding to the second use case.

[0025] Optionally, before executing the first use case, the method further includes:

[0026] Acquire data transmission information between the first use case and the second use case;

[0027] If the data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same compressor.

[0028] Optionally, the acquiring a first data set corresponding to the first use case includes:

[0029] Obtaining input parameters input for the first use case and obtaining output parameters of the first use case;

[0030] Selecting the input parameter and the output parameter to obtain a target parameter corresponding to the first use case;

[0031] The target parameter is added to the first data set.

[0032] According to one aspect of the present application, a model stress testing performance determination device is provided, comprising:

[0033] A use case acquisition unit, used to acquire a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface;

[0034] A use case execution unit, configured to execute the first use case and obtain a first data set corresponding to the first use case;

[0035] The use case execution unit is further used to import the first data set into a second data set corresponding to the second use case, and execute the second use case;

[0036] A performance determination unit is used to obtain a first execution result of the first use case and a second execution result of the second use case, and determine the stress testing performance of the non-funnel model based on the first execution result and the second execution result.

[0037] Optionally, the set importing unit includes a data acquisition subunit and a set importing subunit, and the set importing unit is used to import the first data set into a second data set corresponding to the second use case, including:

[0038] The data acquisition subunit is used to acquire execution data corresponding to the first data set;

[0039] The set importing subunit is used to import the first data set into a second data set corresponding to the second use case if the execution data satisfies a first execution condition.

[0040] Optionally, the execution data is execution duration, and the set importing subunit is used to import the first data set into a second data set corresponding to the second use case if the execution data satisfies a first execution condition, specifically to:

[0041] Obtaining the execution time of the first use case;

[0042] Determining a duration threshold corresponding to the execution duration based on a first request amount corresponding to the first use case and a second request amount corresponding to the second use case, wherein the first request amount is less than the second request amount;

[0043] If the execution time reaches the time threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0044] Optionally, the use case execution unit, when used to execute the second use case, is specifically used to:

[0045] If the execution time reaches the time threshold, the second use case starts to be executed.

[0046] Optionally, the execution data is a data volume, and the set importing subunit is used to import the first data set into a second data set corresponding to the second use case if the execution data satisfies a first execution condition, specifically to:

[0047] Obtaining the data volume corresponding to the first data set;

[0048] If the data volume reaches the data volume threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0049] Optionally, the set importing subunit is used to import the first data set into a second data set corresponding to the second use case if the execution data satisfies the first execution condition, specifically to:

[0050] If the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case, resetting the execution data and reacquiring the first data set;

[0051] If the re-acquired execution data meets the second execution condition, the re-acquired first data set is imported into the second data set corresponding to the second use case.

[0052] Optionally, the apparatus includes a use case distribution unit, and the use case distribution unit is configured to, before executing the first use case:

[0053] Acquire data transmission information between the first use case and the second use case;

[0054] If the data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same compressor.

[0055] Optionally, the set importing unit, when used to obtain the first data set corresponding to the first use case, is specifically used to:

[0056] Obtaining input parameters input for the first use case and obtaining output parameters of the first use case;

[0057] Selecting the input parameter and the output parameter to obtain a target parameter corresponding to the first use case;

[0058] The target parameter is added to the first data set.

[0059] According to one aspect of the present application, a server is provided, including:

[0060] at least one processor; and

[0061] a memory communicatively connected to the at least one processor; wherein,

[0062] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform any one of the methods described in the above aspect.

[0063] According to one aspect of the present application, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute any one of the methods described in the above aspect.

[0064] According to one aspect of the present application, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the computer program implements any one of the methods described in the above aspect.

[0065] In one or more embodiments of the present application, by obtaining a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface, the first use case can be executed, and a first data set corresponding to the first use case can be obtained, and the first data set can be imported into a second data set corresponding to the second use case, and the second use case can be executed, and a first execution result of the first use case and a second execution result of the second use case can be obtained, thereby improving the accuracy of obtaining the execution results, and the time when the second use case starts executing is no earlier than the time when the first use case starts executing, thereby improving the accuracy of obtaining the second execution result, and determining the stress testing performance of the non-funnel model based on the first execution result and the second execution result, thereby reducing the situation where the execution results are inaccurate due to obtaining only the first execution result or the second execution result, and thereby improving the accuracy of determining the model stress testing performance of the non-funnel model.

[0066] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present application.

[0068] Figure 1 A system architecture diagram showing a method for determining model stress testing performance provided by an embodiment of the present application;

[0069] Figure 2 An example schematic diagram of a funnel model provided in an embodiment of the present application is shown;

[0070] Figure 3 An example schematic diagram of a non-funnel model provided in an embodiment of the present application is shown;

[0071] Figure 4 A schematic diagram showing a flow chart of a method for determining model stress testing performance provided in an embodiment of the present application;

[0072] Figure 5 A schematic diagram showing a flow chart of a method for determining model stress testing performance provided in an embodiment of the present application;

[0073] Figure 6 A schematic diagram showing a scenario of a method for determining model stress testing performance according to an embodiment of the present application;

[0074] Figure 7 An example schematic diagram of a terminal interface provided by an embodiment of the present application is shown;

[0075] Figure 8 A schematic diagram showing the structure of a device for determining model stress testing performance provided by an embodiment of the present application is shown;

[0076] Fig. 9 A schematic diagram showing the structure of a device for determining model stress testing performance provided by an embodiment of the present application is shown;

[0077] Fig.10 A schematic diagram showing the structure of a device for determining model stress testing performance provided by an embodiment of the present application is shown;

[0078] Fig.11 A schematic diagram of the structure of a server provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0079] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0080] In the description of the present application, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In the description of the present application, it should be noted that, unless otherwise clearly specified and limited, "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood in specific circumstances. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are an "or" relationship.

[0081] With the development of economy and technology, the pace of life and work intensity have increased. For the convenience of users, various applications have been launched. After the application is released, the server needs to withstand a certain amount of pressure so that it can provide better services to users.

[0082] Figure 1 The system architecture diagram of a method for determining model stress testing performance provided by an embodiment of the present application is shown. Figure 1As shown, the terminal 11 can receive a start instruction input by the user for the application. The terminal 11 can start the application based on the start instruction. When the terminal 11 receives a click instruction for a control in the application, the terminal 11 can send an information acquisition request to the server 13 based on the click instruction. The server 13 can send corresponding display information to the terminal 11 in response to the information acquisition request, so that the terminal 11 can display the corresponding information based on the click instruction.

[0083] In some embodiments, the server can be subjected to stress testing performance determination. For example, a stress testing performance test can be performed on a model in the server. In the server performance stress testing, in order to ensure the authenticity of the performance stress testing as much as possible, for example, simulation can be performed from two aspects: the user's data model and the traffic model, where the traffic model refers to the request path and request ratio of the user to access each service (interface) of the server. The traffic model can include, for example, a funnel model and a non-funnel model.

[0084] According to some embodiments, Figure 2 FIG. 2 shows an example schematic diagram of a funnel model provided by an embodiment of the present application. Figure 2 As shown in the figure, a user's access behavior may go through multiple services (interfaces), but starting from the first interface, the number of requests from subsequent interfaces will not exceed the number of requests from the previous interface. QPS (Queries Per Second) is the number of queries that a server can respond to per second, and is a measure of the amount of traffic a specific query server handles within a specified time. Figure 2 As shown in the figure, there are 100,000 QPS requests to interface 1, then 70,000 QPS requests to interface 2 and 30,000 QPS requests to interface 3, that is, the total number of requests is 100,000 QPS, and the number of requests to interface 2 and interface 3 does not exceed the number of requests to interface 1. As shown in the figure, after 70,000 QPS requests to interface 2, there are 30,000 QPS requests to interface 4 and 20,000 QPS requests to interface 5, among which the number of requests to interface 4 and interface 5 does not exceed the number of requests to interface 2. For example, taking the usage behavior of users of application A as an example, there are 100,000 QPS requests to the discovery page of application A, among which 50,000 QPS will click on the video to view the video information, and 10,000 QPS users will comment on the video. This is a user request path of a funnel traffic model.

[0085] In some embodiments, Figure 3 FIG. 2 shows an example schematic diagram of a non-funnel model provided in an embodiment of the present application. Figure 3 As shown in FIG. 1 , when a user uses an application, a user's one access behavior may go through multiple services. That is, a user's one access may go through multiple interfaces. The multiple interfaces may include, for example, interface 6, interface 7, interface 8, and interface 9. Figure 3As shown, there are 100,000 QPS requesting interface 6, but 500,000 QPS requesting interface 7, that is, the request volume of interface 2 exceeds the request volume of interface 1. For example, the use behavior of users of application A to grab red envelopes is explained as follows: 100,000 QPS will request red envelope IDs, and there will be 500,000 QPS users who use red envelope IDs to share red envelopes. This user behavior of grabbing red envelopes is a typical flash sale activity, which can be a user request path of a non-funnel traffic model.

[0086] In the non-funnel model, the request to the next interface is not a simple repeated amplification of the previous interface. The simple repeated amplification of the request cannot guarantee the uniqueness of the amplified request. Therefore, it is not possible to simply repeat the amplification of the previous interface to obtain accurate model stress testing performance. In addition, in order to simulate the real behavior of users as much as possible, when the subsequent interface with large request traffic uses the data of the previous interface with small request volume, the data generated by the previous interface with small request volume should also continue to be used. For example Figure 3 As shown, interface 1 can spend some time generating a batch of data for interface 2 to use, and then interface 2 uses the data generated by interface 1 while interface 1 is still generating data. Since the request volume corresponding to each interface in the non-funnel model is not necessarily less than the request volume of the previous interface, the accuracy of the model stress test performance determination of the non-funnel model is low.

[0087] The present application is described in detail below with reference to specific embodiments.

[0088] In the first embodiment, if Figure 4 As shown, Figure 4 A flow chart of a method for determining model stress test performance provided by an embodiment of the present application is shown, which can be implemented by a computer program and can be run on a device including an application. The computer program can be integrated into the application or run as an independent tool application.

[0089] Specifically, the method for determining the stress testing performance of the model includes:

[0090] S101, obtaining a first use case and a second use case in a non-funnel model;

[0091] According to some embodiments, the execution subject of the embodiments of the present application may be, for example, a server. The server does not specifically refer to a fixed server. For example, according to actual needs, the server may be a server cluster composed of multiple servers, or may be a server determined based on an application scenario other than a funnel model.

[0092] The model stress test performance determination method of the present application can be applied to the determination of the performance of the non-funnel model, for example. The non-funnel model does not specifically refer to a fixed non-funnel model. For example, when the occasion in which the non-funnel model is applied changes, the non-funnel model will also change accordingly. For example, when the number of interfaces included in the non-funnel model changes, the non-funnel model can also change accordingly.

[0093] It is easy to understand that the first use case and the second use case belong to the same interface. The first use case and the second use case may be two use cases obtained by segmenting a certain interface, for example.

[0094] Optionally, the first use case refers only to the use case that is executed first after the interface is segmented, and the first use case does not specifically refer to a fixed use case. For example, when the interface changes, the first use case obtained by segmenting the interface will also change accordingly.

[0095] In some embodiments, the second use case refers only to the use case executed after the interface is split and the first use case starts to execute, and the second use case does not specifically refer to a fixed use case. For example, when the interface changes, the second use case obtained by splitting the interface will also change accordingly.

[0096] According to some embodiments, when the server executes the model stress testing performance determination method, the server may obtain the first use case and the second use case in the non-funnel model.

[0097] S102, executing a first use case and acquiring a first data set corresponding to the first use case;

[0098] In some embodiments, a set refers to a collection of specific or abstract objects with a certain property. A data set refers to a collection of data with a certain property. A first data set refers to a collection of data obtained after executing a first use case. The first data set includes, but is not limited to, input data input for the first use case and output data obtained after the first use case is executed. The first data may, for example, include only input data input for the first use case, or only output data obtained after the first use case is executed, or part of the input data and output data, etc.

[0099] It is easy to understand that the first data set does not specifically refer to a fixed set. For example, when the type of data included in the first data set changes, the first data set will also change accordingly. For example, when the amount of data included in the first data set changes, the first data set will also change accordingly. For example, when the method for obtaining the first data set changes, the first data set will also change accordingly.

[0100] According to some embodiments, when the server executes the model stress testing performance determination method, the server may obtain a first use case and a second use case in the non-funnel model. The server may execute the first use case and obtain a first data set corresponding to the first use case after starting to execute the first use case.

[0101] S103, importing the first data set into a second data set corresponding to the second use case, and executing the second use case;

[0102] In some embodiments, the second data set refers to a data set corresponding to the second use case. The second data set does not specifically refer to a certain data set. The second data set may, for example, include input data input for the second use case. For example, when the first data set changes, the second data set will also change accordingly. For example, when the method for obtaining the second data set changes, the second data set will also change accordingly. For example, the second data set may be formed by importing only the first data set, or may include the first data set and data input only for the second data set.

[0103] According to some embodiments, when the server obtains the first data set, the server may import the first data set into a second data set corresponding to the second use case. When the server imports the first data set into the data set corresponding to the second use case, the server may execute the second use case.

[0104] It is easy to understand that the second use case starts executing no earlier than the first use case, that is, the second use case is executed after the first use case starts executing. That is, the second use case starts executing after the first use case starts executing, that is, the time point at which the second use case starts executing is after the time point at which the first use case starts executing.

[0105] S104, obtaining a first execution result of the first use case and a second execution result of the second use case, and determining the stress testing performance of the non-funnel model based on the first execution result and the second execution result.

[0106] According to some embodiments, the first execution result refers to the execution result corresponding to the first use case obtained by the server based on the first data set. The first execution result does not specifically refer to a fixed result. For example, when the first data set changes, the first execution result will also change accordingly. For example, when the amount of data included in the first data set changes, the first execution result will also change accordingly.

[0107] In some embodiments, since the first data set includes but is not limited to the input data input for the first use case and the output data obtained after the first use case is executed, when the first data set only includes the input data input for the first use case, the server can obtain the first execution result of the first use case after executing the first use case based on the first data set. When the first data set only includes the output data obtained after the first use case is executed, the server can, for example, directly obtain the first execution result of the first use case based on the output data.

[0108] In some embodiments, the second execution result refers to the execution result corresponding to the second use case. The second execution result does not specifically refer to a fixed result. For example, when the first data set changes, the second data set will also change accordingly, and the second execution result of the second use case obtained by the server based on the second data set will change accordingly.

[0109] It is easy to understand that stress testing is a method for determining the stability of a non-funnel model. Stress testing performance can be used to indicate the ability of a non-funnel model to withstand request pressure. The stress testing performance does not specifically refer to a fixed performance. For example, when the first execution result changes, the stress testing performance of the non-funnel model will also change accordingly. For example, when the second execution result changes, the stress testing performance of the non-funnel model will also change accordingly. For example, when both the first execution result and the second execution result change, the stress testing performance of the non-funnel model will also change accordingly.

[0110] Optionally, when the server executes the model stress testing performance determination method, the server may obtain the first use case and the second use case in the non-funnel model. When the server executes the model stress testing performance determination method, the server may obtain the first use case and the second use case in the non-funnel model. The server may execute the first use case, and after starting to execute the first use case, obtain a first data set corresponding to the first use case. When the server obtains the first data set, the server may import the first data set into the second data set corresponding to the second use case. When the server imports the first data set into the data set corresponding to the second use case, the server may execute the second use case. The server may obtain the first execution result of the first use case and the second execution result of the second use case, and the server may determine the stress testing performance of the non-funnel model based on the first execution result and the second execution result obtained.

[0111] In one or more embodiments of the present application, by obtaining a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface, the first use case can be executed, and a first data set corresponding to the first use case can be obtained, and the first data set can be imported into a second data set corresponding to the second use case, and the second use case can be executed, and a first execution result of the first use case and a second execution result of the second use case can be obtained, thereby improving the accuracy of obtaining the execution results, and the time when the second use case starts executing is no earlier than the time when the first use case starts executing, thereby improving the accuracy of obtaining the second execution result, and determining the stress testing performance of the non-funnel model based on the first execution result and the second execution result, thereby reducing the situation where the execution results are inaccurate due to obtaining only the first execution result or the second execution result, and thereby improving the accuracy of determining the model stress testing performance of the non-funnel model.

[0112] See also Figure 5 , Figure 5 A flow chart of a method for determining model stress testing performance provided by an embodiment of the present application is shown. Specifically:

[0113] S201, obtaining a first use case and a second use case in a non-funnel model;

[0114] The specific process is as described above and will not be repeated here.

[0115] In some embodiments, Figure 6 A schematic diagram of a scenario of a method for determining model stress testing performance according to an embodiment of the present application is shown. Figure 6 As shown, the server can divide interface A into use case 1 and use case 2. Among them, there is a data export and import relationship between use case 1 and use case 2. The data can be, for example, context data. That is, the data corresponding to use case 1 can be exported and imported into the data corresponding to use case 2. Use case 1 and use case 2 can form a scene. The parallel execution of multiple scenes can form a batch job, for example. There can be multiple use cases in a scene, and there is no front-and-back flow dependency relationship of context data between the multiple use cases. Among them, when the server executes multiple use cases, it includes but is not limited to parallel execution or serial execution.

[0116] S202, obtaining data transmission information between the first use case and the second use case;

[0117] In some embodiments, the data transmission information is used to indicate the data transmission between the first use case and the second use case. The data transmission information does not specifically refer to a fixed transmission information. For example, when the data transmission time point of the first use case or the second use case changes, the data transmission information will also change accordingly.

[0118] According to some embodiments, when the server obtains the first use case and the second use case, the server may obtain data transmission information between the first use case and the second use case. For example, when the server obtains use case 1 and use case 2, the server may obtain data transmission information between use case 1 and use case 2.

[0119] If the server does not obtain the data transmission information between the first use case and the second use case, the server can control the first use case and the second use case to be distributed to different compressors.

[0120] S203, if data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same transmitter and compressor;

[0121] According to some embodiments, when the server obtains the first use case and the second use case, the server can obtain data transmission information between the first use case and the second use case. If the server obtains the data transmission information between the first use case and the second use case, the server can distribute the first use case and the second use case to the same stress tester. The server distributes the first use case and the second use case to the same stress tester based on the data transmission information, which can improve the execution efficiency of the first use case and the second use case, and further improve the efficiency of determining the model stress test performance. When the server distributes the first use case and the second use case to the same stress tester, that is, the server can control the same stress tester to execute the first use case and the second use case, for example, multiple stress test cases can be executed in the same stress test program.

[0122] S204, executing a first use case, and acquiring a first data set corresponding to the first use case;

[0123] The specific process is as described above and will not be repeated here.

[0124] According to some embodiments, when the server obtains the first data set corresponding to the first use case, the server may first execute the first use case, and after starting to execute the first use case, the server may, for example, obtain input parameters input for the first use case and obtain output parameters corresponding to the first use case. The server may select input parameters and output parameters, obtain target parameters corresponding to the first use case, and add the target parameters to the first data set. The server's selection of input data and output data may improve the accuracy of data acquisition, may improve the accuracy of the first data set acquisition, and further may improve the accuracy of the model stress testing performance determination. When the server obtains the first data set corresponding to the first use case, the server may store the first data set.

[0125] In some embodiments, Figure 6As shown, use case 1 may correspond to an interface with a small request volume in a non-funnel traffic model, and use case 2 may correspond to an interface with a large request volume in a non-funnel traffic model. The fields exported and stored in use case 1 include id1, name1, response1_1, and reply1_2, where id1 and name1 are part of the input parameters (request parameters) of use case 1, and response1_1 and reply1_2 are part of the output fields (response parameters) of use case 1. The server may select from the stored id1, name1, response1_1, and reply1_2, obtain the target parameters id1 and name1, and add id1 and name1 to the first data set.

[0126] Optionally, the target parameter refers to the data obtained after the server selects the input data and the output data, that is, the target parameter is the selected data. The target parameter does not specifically refer to a fixed parameter. When the selection instruction received by the server changes, the target parameter will also change accordingly. For example, when the input parameter or the output parameter changes, the target parameter will also change accordingly.

[0127] S205, obtaining execution data corresponding to the first data set;

[0128] According to some embodiments, the execution data refers to the data corresponding to the first data set obtained when the server executes the first use case. The execution data does not specifically refer to a fixed data. When the data type included in the execution data changes, the execution data will also change accordingly. When the corresponding acquisition method or acquisition time point of the execution data changes, the execution data will also change accordingly.

[0129] In some embodiments, when the server obtains the first data set corresponding to the first use case, the server may obtain execution data corresponding to the first data set. The execution data includes but is not limited to execution time, data volume, etc.

[0130] S206, if the execution data satisfies the first execution condition, importing the first data set into a second data set corresponding to the second use case, and executing the second use case;

[0131] The specific process is as described above and will not be repeated here.

[0132] In some embodiments, the first execution condition refers to a condition corresponding to the execution data, and the execution condition is used to indicate whether to import the first data set into the second data set corresponding to the second use case. The first execution condition does not specifically refer to a fixed condition. For example, when the server obtains a condition modification instruction for the first execution condition, the first execution condition may also change accordingly. The condition modification instruction includes but is not limited to one directly entered by the user on the server, or sent to the server via a terminal.

[0133] The terminal includes but is not limited to: wearable devices, handheld devices, personal computers, tablet computers, vehicle-mounted devices, smart phones, computing devices or other processing devices connected to wireless modems, etc. In different networks, the terminal can be called different names, such as: user equipment, access server, user unit, user station, mobile station, mobile station, remote station, remote server, mobile device, user server, server, wireless communication equipment, user agent or user device, cellular phone, cordless phone, personal digital assistant (PDA), fifth generation mobile communication technology (5G) network, fourth generation mobile communication technology (4G) network, third generation mobile communication technology (3G) network or terminal in future evolution network, etc.

[0134] According to some embodiments, when the server obtains the execution data corresponding to the first data set, the server may detect the relationship between the execution data corresponding to the first data set and the first execution condition. If the server determines that the execution data satisfies the first execution condition, the server may import the first data set into a second data set corresponding to the second use case and execute the second use case.

[0135] According to some embodiments, the execution data is the execution duration. If the server execution data satisfies the first execution condition, the server can obtain the execution duration of the first use case when importing the first data set into the second data set corresponding to the second use case. When the server obtains the execution duration of the first use case, the server can determine the duration threshold corresponding to the execution duration based on the first request amount corresponding to the first use case and the second request amount of the second use case. Among them, the first request amount is less than the second request amount. If the server determines that the execution duration reaches the duration threshold, the server can determine that the first data set is obtained, and import the first data set into the second data set corresponding to the second use case. The server determines the first data set based on the execution duration, which can improve the accuracy of obtaining the first data set, reduce the situation where the data included in the first data set causes the second use case to fail to execute, and improve the accuracy of determining the model stress testing performance.

[0136] In some embodiments, the execution duration refers to the duration of the server executing the first use case. The execution duration is the duration from the start time point of the server executing the first use case to the execution duration acquisition time point. The execution duration does not specifically refer to a fixed duration. For example, when the execution duration acquisition time point changes, the execution duration may also change accordingly.

[0137] It is easy to understand that the duration threshold refers to the critical value of the duration corresponding to the execution duration. The duration threshold does not specifically refer to a fixed duration threshold. The duration threshold can be, for example, the duration threshold corresponding to the execution duration determined by the server based on the first request amount corresponding to the first use case and the second request amount of the second use case.

[0138] Optionally, the first request volume refers to the quantity requested for the first use case. The first request volume may be, for example, a QPS (Queries Per Second) request volume. QPS refers to the number of queries per second, which is the number of queries that a server can respond to per second, and is a measure of the amount of traffic handled by a specific query server within a specified time. The second request volume refers to the quantity requested for the second use case. The first request volume is less than the second request volume. A request received by the server may be, for example, a request initiated by a terminal based on a request instruction obtained for an application. The request instruction received by the terminal may be, for example, a click request instruction. In this case, an example schematic diagram of the terminal interface may be, for example, as shown below. Figure 7 shown.

[0139] In some embodiments, the first use case may be, for example, use case 1, and the second use case may be, for example, use case 2. The execution data is the execution duration. The first execution condition may be, for example, that the execution duration satisfies the duration threshold, that is, the first execution condition may be, for example, that the execution duration is greater than or equal to the duration threshold. The first QPS request amount corresponding to the first use case obtained by the server may be, for example, 500,000 QPS requests, and the second QPS request amount corresponding to the second use case obtained may be, for example, 1 million QPS requests. The duration threshold may be, for example, 120 seconds. When the server obtains that the execution duration is 120 seconds, that is, the server determines that the execution duration of 120 seconds reaches the duration threshold of 120 seconds, the server may determine that the first data set is obtained, and import the first data set into the second data set corresponding to the second use case.

[0140] In some embodiments, the execution data may be, for example, execution duration. When the server imports the second data set corresponding to the second use case into the first data set and executes the second use case, the server may determine whether the execution duration reaches a duration threshold. If the server determines that the execution duration reaches the duration threshold, the server may start executing the second use case.

[0141] It is easy to understand that the first QPS request amount corresponding to the first use case obtained by the server may be, for example, 500,000 QPS requests, and the second QPS request amount corresponding to the second use case obtained may be, for example, 1 million QPS requests. The duration threshold may be, for example, 120 seconds. When the server obtains that the execution duration is 120 seconds, that is, the server determines that the execution duration of 120 seconds reaches the duration threshold of 120 seconds, the server may start executing the second use case.

[0142] According to some embodiments, the execution data is the data volume, and if the server execution data satisfies the first execution condition, the data volume corresponding to the first data set can be obtained when the first data set is imported into the second data set corresponding to the second use case. If the data volume reaches the data volume threshold, the server can determine that the first data set is obtained, and import the first data set into the second data set corresponding to the second use case. The server determines the first data set based on the data volume, which can improve the accuracy of obtaining the first data set, reduce the situation where the data included in the first data set causes the second use case to fail to execute, and improve the accuracy of determining the model stress testing performance.

[0143] In some embodiments, the data volume is used to indicate the number of items included in the first data set. The data volume does not specifically refer to a fixed duration. For example, when the execution duration of the first use case changes, the data volume will also change accordingly. For example, when the execution efficiency of the first use case changes, the data volume will also change accordingly.

[0144] It is easy to understand that the data volume threshold refers to a critical value corresponding to the data volume, and the data volume threshold does not specifically refer to a fixed threshold. For example, threshold setting instructions that can be obtained for different interface servers. For example, when the request volume for the first use case or the second use case changes, the data volume threshold can also change accordingly.

[0145] Optionally, the data volume corresponding to the first data set acquired by the server may be, for example, 201,000 data volumes. The data volume threshold may be, for example, 200,000 data volumes. If the data volume of 201,000 data volumes reaches the data volume threshold of 200,000 data volumes, the server may determine that the first data set is acquired, and import the first data set into a second data set corresponding to the second use case.

[0146] In some embodiments, the execution data may be, for example, data volume. When the server imports the first data set into the second data set corresponding to the second use case and executes the second use case, the server may determine whether the data volume corresponding to the first data set reaches a data volume threshold. If the server determines that the data volume reaches the data volume threshold, the server may start executing the second use case.

[0147] It is easy to understand that when the server obtains the data volume corresponding to the first data set, the server can, for example, obtain the data volume once every preset time period. The data volume obtained by the server can be, for example, 201,000 data volumes. The data volume threshold can be, for example, 200,000 data volumes. If the data volume 201,000 data volumes reaches the data volume threshold 200,000 data volumes, the server can start executing the second use case.

[0148] According to some embodiments, if the execution data satisfies the first execution condition, when the first data set is imported into the second data set corresponding to the second use case, if the execution data satisfies the first execution condition, the server may import the first data set into the second data set corresponding to the second use case, and reset the execution data and reacquire the first data set. If the reacquired execution data satisfies the second execution condition, the reacquired first data set is imported into the second data set corresponding to the second use case. The server resets the execution data and reacquires the first data set, and can import the reacquired first data set into the second data set in a timely manner, reducing the excessive data stored in the first data set, so that the data exported from the first use case can be imported into the second data set in a timely manner, reducing the storage time of the data, and improving the efficiency of determining the model stress testing performance.

[0149] In some embodiments, the first use case may be, for example, use case 1, and the second use case may be, for example, use case 2. The execution data is the execution duration. The first execution condition may be, for example, that the execution duration satisfies the duration threshold, that is, the first execution condition may be, for example, that the execution duration is greater than or equal to the duration threshold, and the duration threshold may be, for example, 120 seconds. The first QPS request amount corresponding to the first use case obtained by the server may be, for example, 500,000 QPS requests, and the second QPS request amount corresponding to the second use case obtained may be, for example, 1 million QPS requests. When the server obtains that the execution duration is 120 seconds, that is, the server determines that the execution duration of 120 seconds reaches the duration threshold of 120 seconds, the server may determine that the first data set is obtained, and import the first data set into the second data set corresponding to the second use case. After the server imports the first data set into the second data set corresponding to the second use case, the server may reset the execution duration, and re-acquire the execution duration and the first data set. The second execution condition may be, for example, that the execution duration satisfies the duration threshold, that is, the second execution condition may be, for example, that the execution duration is greater than or equal to the duration threshold, and the duration threshold may be, for example, 120 seconds. When the execution time re-acquired by the server is 120 seconds, that is, the server determines that the execution time of 120 seconds reaches the time threshold of 120 seconds, the server can determine that the first data set is re-acquired and import the first data set into the second data set corresponding to the second use case again.

[0150] In some embodiments, the second execution condition refers to a condition for judging the execution data after the execution data is reset. The second execution condition may be consistent with the first execution condition or inconsistent with the first execution condition. For example, when the execution data is the execution duration, the duration threshold corresponding to the first execution condition may be, for example, 120 seconds, and the duration threshold corresponding to the second execution condition may also be, for example, 120 seconds. For example, when the execution data is the execution duration, the duration threshold corresponding to the first execution condition may be, for example, 120 seconds, and the duration threshold corresponding to the second execution condition may be, for example, 140 seconds.

[0151] According to some embodiments, the server imports the first data set into the second data set corresponding to the second use case at least once. If the first data set obtained by the server for the first time meets the set requirement, the server imports the first data set into the second data set corresponding to the second use case only once.

[0152] S207, obtaining a first execution result of the first use case and a second execution result of the second use case, and determining the stress testing performance of the non-funnel model based on the first execution result and the second execution result.

[0153] The specific process is as described above and will not be repeated here.

[0154] In some embodiments, when the server obtains the data transmission information between the first use case and the second use case, the first use case and the second use case can be distributed to the compressor. For example, the server can control the H compressor to execute the first use case and obtain the first data set corresponding to the first use case. When the server imports the first data set into the second data set, it can control the H compressor to execute the second use case. The server can obtain the first execution result of the first use case and the second execution result of the second use case through the same compressor, which can improve the execution efficiency of the first use case and the second use case, and further improve the efficiency of determining the model stress testing performance.

[0155] Optionally, the server may obtain the first execution result and the second execution result at the same time, or may obtain the first execution result and the second execution result at different time points.

[0156] It is easy to understand that after the server determines the non-funnel model stress test performance, the server can apply the non-funnel model to the application, that is, the server can provide services to users who use the application based on the non-funnel model. Therefore, the server's determination of the non-funnel model stress test performance can be used to indicate the improvement of the performance of the non-funnel model, so as to improve the stability of the non-funnel model and improve the user experience.

[0157] In one or more embodiments of the present application, by obtaining the first use case and the second use case in the non-funnel model, obtaining the data transmission information between the first use case and the second use case, if the data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same pressure machine, which can improve the execution efficiency of the first use case and the second use case, and thus improve the efficiency of determining the model stress test performance. Secondly, the first use case is executed, and the first data set corresponding to the first use case is obtained, the execution data corresponding to the first data set can be obtained, and when the execution data meets the first execution condition, the first data set is imported into the second data set corresponding to the second use case, and then the second use case is executed. The server determines the first data set based on the execution data, which can improve the accuracy of obtaining the first data set, reduce the situation where the data included in the first data set causes the second use case to be unable to execute, and improve the accuracy of determining the model stress test performance. Finally, the second use case is executed after the first user starts to execute, which can improve the accuracy of obtaining the second execution result, reduce the situation where only the first execution result or the second execution result is obtained, resulting in inaccurate execution result acquisition, and improve the accuracy of determining the model stress test performance of the non-funnel model.

[0158] The following are device embodiments of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0159] See also Figure 8, which shows a schematic diagram of the structure of a model stress test performance determination device provided in an embodiment of the present application. The model stress test performance determination device can be implemented as all or part of the device through software, hardware, or a combination of both. The model stress test performance determination device 800 includes a use case acquisition unit 801, a use case execution unit 802, and a performance determination unit 803, wherein:

[0160] A use case acquisition unit 801 is used to acquire a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface;

[0161] A use case execution unit 802, configured to execute a first use case and obtain a first data set corresponding to the first use case;

[0162] The use case execution unit 802 is further configured to import the first data set into a second data set corresponding to the second use case, and execute the second use case;

[0163] The performance determination unit 803 is used to obtain a first execution result of the first use case and a second execution result of the second use case, and determine the stress testing performance of the non-funnel model based on the first execution result and the second execution result.

[0164] According to some embodiments, Fig. 9 A schematic diagram of the structure of a device for determining model stress testing performance provided by an embodiment of the present application is shown. Fig. 9 As shown, the use case execution unit 802 includes a data acquisition subunit 812 and a collection import subunit 822. The use case execution unit 802 is used to import the first data set into the second data set corresponding to the second use case, including:

[0165] The data acquisition subunit 812 is used to acquire the execution data corresponding to the first data set;

[0166] The set importing subunit 822 is used to import the first data set into the second data set corresponding to the second use case if the execution data meets the first execution condition.

[0167] According to some embodiments, the execution data is the execution duration, and the set importing subunit 822 is used to import the first data set into the second data set corresponding to the second use case if the execution data satisfies the first execution condition, specifically for:

[0168] Get the execution time of the first use case;

[0169] Determining a duration threshold corresponding to the execution duration based on a first request amount corresponding to the first use case and a second request amount of the second use case, wherein the first request amount is less than the second request amount;

[0170] If the execution time reaches the time threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0171] According to some embodiments, the use case execution unit 902, when used to execute the second use case, is specifically used to:

[0172] If the execution time reaches the time threshold, the second use case starts to be executed.

[0173] According to some embodiments, the execution data is a data volume, and the set import subunit 822 is used to import the first data set into the second data set corresponding to the second use case if the execution data satisfies the first execution condition, specifically for:

[0174] Obtaining the data volume corresponding to the first data set;

[0175] If the data volume reaches the data volume threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0176] According to some embodiments, the set importing subunit 822 is used to import the first data set into the second data set corresponding to the second use case if the execution data satisfies the first execution condition, specifically to:

[0177] If the execution data satisfies the first execution condition, importing the first data set into a second data set corresponding to the second use case, resetting the execution data and reacquiring the first data set;

[0178] If the re-acquired execution data meets the second execution condition, the re-acquired first data set is imported into the second data set corresponding to the second use case.

[0179] According to some embodiments, Fig.10 A schematic diagram of the structure of a device for determining model stress testing performance provided by an embodiment of the present application is shown. Fig.10 As shown, the apparatus includes a use case distribution unit 804, and the use case distribution unit 804 is used before executing the first use case;

[0180] Acquire data transmission information between the first use case and the second use case;

[0181] If the data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same compressor.

[0182] According to some embodiments, the use case execution unit 802, when used to obtain a first data set corresponding to a first use case, is specifically used to:

[0183] Obtaining input parameters input for the first use case and obtaining output parameters of the first use case;

[0184] Selecting input parameters and output parameters to obtain target parameters corresponding to the first use case;

[0185] A target parameter is added to the first data set.

[0186] It should be noted that the model stress test performance determination device provided in the above embodiment only uses the division of the above functional modules as an example when executing the model stress test performance determination method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the model stress test performance determination device provided in the above embodiment and the model stress test performance determination method embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0187] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0188] In one or more embodiments of the present application, a use case acquisition unit can acquire a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface, a use case execution unit can execute the first use case and acquire a first data set corresponding to the first use case, and the use case execution unit can also import the first data set into a second data set corresponding to the second use case and execute the second use case, thereby improving the accuracy of acquiring the execution result, and the time when the second use case starts executing is no earlier than the time when the first use case starts executing, thereby improving the accuracy of acquiring the second execution result, and a performance determination unit can determine the stress testing performance of the non-funnel model based on the first execution result and the second execution result, thereby reducing the situation where only acquiring the first execution result or the second execution result leads to inaccurate execution result acquisition, thereby improving the accuracy of determining the model stress testing performance of the non-funnel model.

[0189] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 4-Figure 7 The model stress test performance determination method of the embodiment shown in the figure can be found in the specific execution process. Figure 4-Figure 7 The specific description of the illustrated embodiment will not be repeated here.

[0190] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figure 4-Figure 7 The model stress test performance determination method of the embodiment shown in the figure can be found in the specific execution process. Figure 4-Figure 7 The specific description of the illustrated embodiment will not be repeated here.

[0191] See also Fig.11 , is a schematic diagram of the structure of a server provided in an embodiment of the present application. Fig.11 As shown, the server 1100 may include: at least one processor 1101 , at least one network interface 1104 , a user interface 1103 , a memory 1105 , and at least one communication bus 1102 .

[0192] The communication bus 1102 is used to realize the connection and communication between these components.

[0193] The user interface 1103 may include a speaker and a display screen, and the optional user interface 1103 may also include a standard wired interface and a wireless interface.

[0194] The network interface 1104 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0195] Among them, the processor 1101 may include one or more processing cores. The processor 1101 uses various interfaces and lines to connect various parts within the entire server 1100, and executes various functions and processes data of the server 1100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1105, and calling data stored in the memory 1105. Optionally, the processor 1101 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 1101 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1101, and it can be implemented separately through a chip.

[0196] Among them, the memory 1105 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 1105 includes a non-transitory computer-readable storage medium. The memory 1105 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1105 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 1105 may also be optionally at least one storage device located away from the aforementioned processor 1101. As Fig.11 As shown, the memory 1105 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an application program for determining model stress testing performance.

[0197] exist Fig.11 In the server 1100 shown, the user interface 1103 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 1101 can be used to call the application program for determining the model stress test performance stored in the memory 1105, and specifically perform the following operations:

[0198] Obtain a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface;

[0199] Execute a first use case and obtain a first data set corresponding to the first use case;

[0200] Importing the first data set into a second data set corresponding to a second use case, and executing the second use case;

[0201] The second use case starts executing no earlier than the first use case starts executing;

[0202] A first execution result of the first use case and a second execution result of the second use case are obtained, and based on the first execution result and the second execution result, a stress testing performance of the non-funnel model is determined.

[0203] According to some embodiments, when the processor 1101 is configured to import the first data set into the second data set corresponding to the second use case, the following operations are specifically performed:

[0204] Obtaining execution data corresponding to the first data set;

[0205] If the execution data satisfies the first execution condition, the first data set is imported into a second data set corresponding to the second use case.

[0206] According to some embodiments, the execution data is execution duration, and the processor 1101 is configured to import the first data set into a second data set corresponding to the second use case if the execution data satisfies the first execution condition, including:

[0207] Get the execution time of the first use case;

[0208] Determining a duration threshold corresponding to the execution duration based on a first request amount corresponding to the first use case and a second request amount of the second use case, wherein the first request amount is less than the second request amount;

[0209] If the execution time reaches the time threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0210] According to some embodiments, when the processor 1101 is used to execute the second use case, the following operations are specifically performed:

[0211] If the execution time reaches the time threshold, the second use case starts to be executed.

[0212] According to some embodiments, the execution data is a data volume, and the processor 1101 is used to execute if the execution data satisfies the first execution condition, then import the first data set into the second data set corresponding to the second use case, and specifically perform the following operations:

[0213] Obtaining the data volume corresponding to the first data set;

[0214] If the data volume reaches the data volume threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

[0215] According to some embodiments, the processor 1101 is configured to execute the following operations when, if the execution data satisfies the first execution condition, the first data set is imported into the second data set corresponding to the second use case:

[0216] If the execution data satisfies the first execution condition, importing the first data set into a second data set corresponding to the second use case, resetting the execution data and reacquiring the first data set;

[0217] If the re-acquired execution data meets the second execution condition, the re-acquired first data set is imported into the second data set corresponding to the second use case.

[0218] According to some embodiments, the processor 1101 is configured to perform the following operations before executing the first use case:

[0219] Acquire data transmission information between the first use case and the second use case;

[0220] If the data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same compressor.

[0221] According to some embodiments, when the processor 1101 is configured to execute acquiring a first data set corresponding to a first use case, the following operations are specifically performed:

[0222] Obtaining input parameters input for the first use case and obtaining output parameters of the first use case;

[0223] Selecting input parameters and output parameters to obtain target parameters corresponding to the first use case;

[0224] A target parameter is added to the first data set.

[0225] In one or more embodiments of the present application, by obtaining a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface, the first use case can be executed, and a first data set corresponding to the first use case can be obtained, and the first data set can be imported into a second data set corresponding to the second use case, and the second use case can be executed, and a first execution result of the first use case and a second execution result of the second use case can be obtained, thereby improving the accuracy of obtaining the execution results, and the time when the second use case starts executing is no earlier than the time when the first use case starts executing, thereby improving the accuracy of obtaining the second execution result, and determining the stress testing performance of the non-funnel model based on the first execution result and the second execution result, thereby reducing the situation where the execution results are inaccurate due to obtaining only the first execution result or the second execution result, and thereby improving the accuracy of determining the model stress testing performance of the non-funnel model.

[0226] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the above method are implemented. The computer-readable storage medium may include, but is not limited to, any type of disk, including a floppy disk, an optical disk, a DVD, a CD-ROM, a micro drive, and a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory device, a magnetic card or an optical card, a nanosystem (including a molecular memory IC), or any type of medium or device suitable for storing instructions and / or data.

[0227] An embodiment of the present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute part or all of the steps of any server status determination method recorded in the above method embodiments.

[0228] Those skilled in the art can clearly understand that the technical solution of the present application can be implemented with the help of software and / or hardware. The "unit" and "module" in this specification refer to software and / or hardware that can independently complete or cooperate with other components to complete specific functions, where the hardware can be, for example, a field programmable gate array (FPGA), an integrated circuit (IC), etc.

[0229] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

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

[0231] In the several embodiments provided in the present application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of the units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units 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 through some service interfaces, and the indirect coupling or communication connection of devices or units can be electrical or other forms.

[0232] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0233] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0234] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, disk or optical disk and other media that can store program code.

[0235] A person skilled in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by entering a program to instruct the relevant hardware. The program may be stored in a computer-readable memory, and the memory may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0236] The above is only an exemplary embodiment of the present application, and the scope of the present application cannot be limited by this. That is, any equivalent changes and modifications made according to the teachings of the present application are still within the scope of the present application. After considering the specification and practicing the application here, those skilled in the art will easily think of other embodiments of the present application. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not recorded in the present application. The specification and examples are only regarded as exemplary, and the scope and spirit of the present application are defined by the claims.

Claims

1. A method for determining model stress testing performance, characterized in that: include: Acquire a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface; Execute the first use case and obtain a first data set corresponding to the first use case; Importing the first data set into a second data set corresponding to the second use case, and executing the second use case; The execution time of the second use case starts no earlier than the execution time of the first use case starts; Obtaining a first execution result of the first use case and a second execution result of the second use case, and determining the stress testing performance of the non-funnel model based on the first execution result and the second execution result; Before executing the first use case, the method further includes: Acquire data transmission information between the first use case and the second use case; If data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same compressor; If the data transmission information between the first use case and the second use case is not obtained, the first use case and the second use case are distributed to different transmitters.

2. The method according to claim 1, characterized in that The importing the first data set into a second data set corresponding to the second use case includes: Obtaining execution data corresponding to the first data set; If the execution data satisfies a first execution condition, the first data set is imported into a second data set corresponding to the second use case.

3. The method according to claim 2, characterized in that The execution data is execution duration, and if the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case includes: Obtaining the execution time of the first use case; Determining a duration threshold corresponding to the execution duration based on a first request amount corresponding to the first use case and a second request amount corresponding to the second use case, wherein the first request amount is less than the second request amount; If the execution time reaches the time threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

4. The method according to claim 3, characterized in that The executing the second use case includes: If the execution time reaches the time threshold, the second use case starts to be executed.

5. The method according to claim 2, characterized in that: The execution data is a data volume, and if the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case includes: Obtaining the data volume corresponding to the first data set; If the data volume reaches the data volume threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

6. The method according to claim 2, characterized in that If the execution data satisfies the first execution condition, importing the first data set into a second data set corresponding to the second use case includes: If the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case, resetting the execution data and reacquiring the first data set; If the re-acquired execution data meets the second execution condition, the re-acquired first data set is imported into the second data set corresponding to the second use case.

7. The method according to claim 1, characterized in that The acquiring a first data set corresponding to the first use case includes: Obtaining input parameters input for the first use case and obtaining output parameters of the first use case; Selecting the input parameter and the output parameter to obtain a target parameter corresponding to the first use case; The target parameter is added to the first data set.

8. A device for determining model stress testing performance, characterized in that: include: A use case acquisition unit, used to acquire a first use case and a second use case in a non-funnel model, wherein the first use case and the second use case belong to the same interface; A use case execution unit, configured to execute the first use case and obtain a first data set corresponding to the first use case; The use case execution unit is further used to import the first data set into a second data set corresponding to the second use case, and execute the second use case; a performance determination unit, configured to obtain a first execution result of the first use case and a second execution result of the second use case, and determine the stress testing performance of the non-funnel model based on the first execution result and the second execution result; The apparatus includes a use case distribution unit, and the use case distribution unit is configured to, before executing the first use case: Acquire data transmission information between the first use case and the second use case; If data transmission information between the first use case and the second use case is obtained, the first use case and the second use case are distributed to the same compressor; If the data transmission information between the first use case and the second use case is not obtained, the first use case and the second use case are distributed to different transmitters.

9. The device according to claim 8, characterized in that The set importing unit includes a data acquisition subunit and a set importing subunit, and the set importing unit is used to import the first data set into a second data set corresponding to the second use case, including: The data acquisition subunit is used to acquire the execution data corresponding to the first data set; The set importing subunit is used to import the first data set into a second data set corresponding to the second use case if the execution data satisfies a first execution condition.

10. The device according to claim 9, characterized in that The execution data is the execution duration, and the set importing subunit is used to import the first data set into the second data set corresponding to the second use case if the execution data satisfies the first execution condition, specifically for: Obtaining the execution time of the first use case; Determining a duration threshold corresponding to the execution duration based on a first request amount corresponding to the first use case and a second request amount corresponding to the second use case, wherein the first request amount is less than the second request amount; If the execution time reaches the time threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

11. The device according to claim 10, characterized in that The use case execution unit, when used to execute the second use case, is specifically used to: If the execution time reaches the time threshold, the second use case starts to be executed.

12. The device according to claim 9, characterized in that The execution data is a data volume, and the set importing subunit is used to import the first data set into a second data set corresponding to the second use case if the execution data satisfies a first execution condition, specifically for: Obtaining the data volume corresponding to the first data set; If the data volume reaches the data volume threshold, it is determined that the first data set is acquired, and the first data set is imported into a second data set corresponding to the second use case.

13. The device according to claim 9, characterized in that The set importing subunit is used to import the first data set into the second data set corresponding to the second use case if the execution data satisfies the first execution condition, specifically to: If the execution data satisfies a first execution condition, importing the first data set into a second data set corresponding to the second use case, resetting the execution data and reacquiring the first data set; If the re-acquired execution data meets the second execution condition, the re-acquired first data set is imported into the second data set corresponding to the second use case.

14. The device according to claim 8, characterized in that The set importing unit, when used to obtain the first data set corresponding to the first use case, is specifically used to: Obtaining input parameters input for the first use case and obtaining output parameters of the first use case; Selecting the input parameter and the output parameter to obtain a target parameter corresponding to the first use case; The target parameter is added to the first data set.

15. A server, comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

16. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-7.

17. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 7.

Images