CN114020617A - Model pressure measurement performance determination method and device, server and storage medium - Google Patents

Model pressure measurement performance determination method and device, server and storage medium Download PDF

Info

Publication number
CN114020617A
CN114020617A CN202111274717.1A CN202111274717A CN114020617A CN 114020617 A CN114020617 A CN 114020617A CN 202111274717 A CN202111274717 A CN 202111274717A CN 114020617 A CN114020617 A CN 114020617A
Authority
CN
China
Prior art keywords
use case
data set
execution
data
case
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111274717.1A
Other languages
Chinese (zh)
Inventor
田欧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202111274717.1A priority Critical patent/CN114020617A/en
Publication of CN114020617A publication Critical patent/CN114020617A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3604Software analysis for verifying properties of programs
    • G06F11/3612Software analysis for verifying properties of programs by runtime analysis
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3696Methods or tools to render software testable

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Measuring Fluid Pressure (AREA)

Abstract

The application relates to the technical field of big data intelligent analysis, in particular to a method and a device for determining model pressure measurement performance, a server and a storage medium. A method of model pressure measurement performance determination, comprising: acquiring 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 acquiring 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 time for starting execution of the second case is not earlier than the time for starting execution of the first case; and acquiring a first execution result of the first use case and a second execution result of the second use case, and determining the pressure measurement performance of the non-funnel model based on the first execution result and the second execution result. By the method and the device, accuracy of determining the model pressure measurement performance of the non-funnel model can be improved.

Description

Model pressure measurement performance determination method and device, server and storage medium
Technical Field
The application relates to the technical field of big data intelligent analysis, in particular to a method and a device for determining model pressure measurement performance, a server and a storage medium.
Background
With the development of economic technology, the pace of life and the intensity of work have increased, and various application programs have been operated for the convenience of use by users. After the application program is released, the model used by the server needs to bear certain pressure, so that when the number of the application program using users reaches a certain number, the corresponding service can be provided. Therefore, the determination of the pressure measurement performance of the model becomes a major concern of the user.
Disclosure of Invention
The application provides a method and a device for determining model pressure measurement performance, a server and a storage medium, and mainly aims to improve the accuracy of determining the model pressure measurement performance of a non-funnel model.
According to an aspect of the present application, there is provided a model pressure measurement performance determination method, including:
acquiring 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 acquiring 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 time for starting execution of the second case is not earlier than the time for starting execution of the first case;
and acquiring a first execution result of the first use case and a second execution result of the second use case, and determining the pressure measurement performance of the non-funnel model based on the first execution result and the second execution result.
Optionally, the importing the first data set into a second data set corresponding to the second use case includes:
acquiring execution data corresponding to the first data set;
and if the execution data meets a first execution condition, importing the first data set into a second data set corresponding to the second use case.
Optionally, the executing data is an executing duration, and if the executing data meets a first executing condition, importing the first data set into a second data set corresponding to the second example, where the importing includes:
acquiring the execution duration of the first use case;
determining a time length threshold value corresponding to the execution time length based on a first request quantity corresponding to the first use case and a second request quantity of the second use case, wherein the first request quantity is smaller than the second request quantity;
and if the execution duration reaches the duration threshold, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second example.
Optionally, the executing the second use case includes:
and if the execution duration reaches the duration threshold, starting to execute the second use case.
Optionally, the executing data is a data volume, and if the executing data meets a first executing condition, importing the first data set into a second data set corresponding to the second example, where the importing includes:
acquiring a data volume corresponding to the first data set;
and if the data volume reaches the data volume threshold value, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second use case.
Optionally, if the execution data meets a first execution condition, importing the first data set into a second data set corresponding to the second example, where the importing includes:
if the execution data meets a first execution condition, importing the first data set into a second data set corresponding to the second instance, resetting the execution data and reacquiring the first data set;
and if the newly acquired execution data meets a second execution condition, importing the newly acquired first data set into a second data set corresponding to the second use case.
Optionally, before the executing the first example, the method further includes:
acquiring data transmission information between the first use case and the second use case;
and if the data transmission information between the first use case and the second use case is acquired, distributing the first use case and the second use case to the same transmitter.
Optionally, the acquiring a first data set corresponding to the first case includes:
acquiring input parameters input aiming at the first use case and acquiring output parameters of the first use case;
selecting the input parameters and the output parameters to obtain target parameters corresponding to the first case;
adding the target parameter to a first set of data.
According to an aspect of the present application, there is provided a model pressure measurement performance determination apparatus including:
the device comprises a use case acquisition unit, a processing unit and a processing unit, wherein the use case acquisition unit is used for acquiring a first use case and a second use case in a non-funnel model, and the first use case and the second use case belong to the same interface;
the case execution unit is used for executing the first case and acquiring a first data set corresponding to the first case;
the case execution unit is further used for importing the first data set into a second data set corresponding to the second case and executing the second case;
and the performance determining unit is used for acquiring a first execution result of the first use case and a second execution result of the second use case, and determining the pressure measurement performance of the non-funnel model based on the first execution result and the second execution result.
Optionally, the set importing unit includes a data obtaining subunit and a set importing subunit, where the set importing unit is configured to import the first data set into a second data set corresponding to the second use case, and includes:
the data acquisition subunit is configured to acquire execution data corresponding to the first data set;
the set importing subunit is configured 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.
Optionally, the execution data is an execution duration, and the set importing subunit is configured to, when the execution data satisfies a first execution condition, import the first data set into a second data set corresponding to the second example, specifically:
acquiring the execution duration of the first use case;
determining a time length threshold value corresponding to the execution time length based on a first request quantity corresponding to the first use case and a second request quantity of the second use case, wherein the first request quantity is smaller than the second request quantity;
and if the execution duration reaches the duration threshold, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second example.
Optionally, the use case execution unit, when configured to execute the second use case, is specifically configured to:
and if the execution duration reaches the duration threshold, starting to execute the second use case.
Optionally, the execution data is a data volume, and the set importing subunit is configured to, when the execution data satisfies a first execution condition, import the first data set into a second data set corresponding to the second example, specifically:
acquiring a data volume corresponding to the first data set;
and if the data volume reaches the data volume threshold value, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second use case.
Optionally, the set importing subunit is configured to, when the first data set is imported into a second data set corresponding to the second example if the execution data meets a first execution condition, specifically:
if the execution data meets a first execution condition, importing the first data set into a second data set corresponding to the second instance, resetting the execution data and reacquiring the first data set;
and if the newly acquired execution data meets a second execution condition, importing the newly acquired first data set into a second data set corresponding to the second use case.
Optionally, the apparatus includes a use case distribution unit, where the use case distribution unit is configured to, before executing the first use case:
acquiring data transmission information between the first use case and the second use case;
and if the data transmission information between the first use case and the second use case is acquired, distributing the first use case and the second use case to the same transmitter.
Optionally, the set importing unit is configured to, when acquiring the first data set corresponding to the first instance, specifically:
acquiring input parameters input aiming at the first use case and acquiring output parameters of the first use case;
selecting the input parameters and the output parameters to obtain target parameters corresponding to the first case;
adding the target parameter to a first set of data.
According to an aspect of the present application, there is provided a server including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of the preceding aspects.
According to an aspect of the application, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of the preceding aspects.
According to an aspect of the application, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the method of any of the preceding aspects.
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, where the first use case and the second use case belong to a same interface, the first use case may be executed, 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, obtaining a first execution result of the first use case and a second execution result of the second use case, the accuracy of obtaining the execution result may be improved, and the time for starting execution of the second use case is not earlier than the time for starting execution of the first use case, the accuracy of obtaining the second execution result may be improved, the pressure measurement performance of the non-funnel model is determined based on the first execution result and the second execution result, and the situation that the execution result is inaccurate due to obtaining only the first execution result or the second execution result may be reduced, the accuracy of determining the model pressure measurement performance of the non-funnel model can be improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present application, nor do they limit the scope of the present application. Other features of the present application will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
fig. 1 is a system architecture diagram illustrating a method for determining a pressure measurement performance of a model according to an embodiment of the present application;
fig. 2 is an exemplary schematic diagram of a funnel model provided in an embodiment of the present application;
FIG. 3 illustrates an exemplary diagram of a non-funnel model provided by an embodiment of the present application;
fig. 4 is a schematic flow chart of a method for determining a pressure measurement performance of a model provided in an embodiment of the present application;
fig. 5 is a schematic flow chart of a method for determining a pressure measurement performance of a model provided in an embodiment of the present application;
FIG. 6 is a schematic view of a scenario illustrating a method for determining a pressure measurement performance of a model according to an embodiment of the present application;
fig. 7 is a schematic diagram illustrating an example of a terminal interface provided in an embodiment of the present application;
fig. 8 is a schematic structural diagram of a model pressure measurement performance determination apparatus according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a model pressure measurement performance determination apparatus according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a model pressure measurement performance determination apparatus according to an embodiment of the present application;
fig. 11 shows a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present application, it is noted that, unless explicitly stated or limited otherwise, "including" and "having" and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art. Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
With the development of economic technology, the pace of life and the intensity of work have increased, and various application programs have been operated for the convenience of use by users. After the application is released, the server needs to bear a certain pressure so that the user can be provided with better service.
Fig. 1 is a system architecture diagram illustrating a method for determining a pressure measurement performance of a model according to an embodiment of the present application. As shown in fig. 1, the terminal 11 may receive a start instruction input by a user for an application program. The terminal 11 may start the application based on the start instruction. When the terminal 11 receives a click command for a control in an application, the terminal 11 may issue an information acquisition request to the server 13 based on the click command. The server 13 may send corresponding presentation information to the terminal 11 for the information acquisition request, so that the terminal 11 may present the corresponding information based on the click command.
In some embodiments, the determination of the pressure measurement performance may be made to the server. For example, a pressure measurement performance test may be performed for the model in the server. In the performance pressure measurement of the server, in order to ensure the authenticity of the performance pressure measurement as much as possible, simulation may be performed from two aspects, such as a data model and a traffic model of a user, where the traffic model refers to a request path and a request proportion of a user accessing each service (interface) of the server. The flow models may include, for example, funnel models and non-funnel models.
According to some embodiments, fig. 2 shows an exemplary schematic diagram of a funnel model provided in embodiments of the present application. As shown in fig. 2, a user may experience multiple services (interfaces) with one access, but the request amount of the subsequent interface does not exceed the request amount of the previous interface from the first interface. Qps (queries Per second) is the number of queries a server can respond to Per second, and is a measure of how much traffic a particular query server processes within a specified time. As shown in fig. 2, there are 10 ten thousand QPS request interfaces 1, then 7 ten thousand QPS request interfaces 2 and 3 ten QPS request interfaces 3, that is, the total amount of QPS requests is 10 ten thousand, and the requests of interfaces 2 and 3 do not exceed the requests of interface 1. As shown, after 7 ten thousand QPS request interfaces 2, there are 3 thousand QPS request interfaces 4 and 2 ten thousand QPS request interfaces 5, where the request amount of interface 4 and interface 5 does not exceed the request amount of interface 2. For example, using behavior of a user using an a application is exemplified, 10 ten thousand QPS requests a discovery page of the a application, wherein 5 ten thousand QPS clicks a video to view video information, and 1 ten thousand QPS users comment the video, which is a user request path of a funnel flow model.
In some embodiments, fig. 3 illustrates an example schematic diagram of a non-funnel model provided by embodiments of the present application. As shown in fig. 3, when a user uses an application, the user's one-access behavior may experience multiple services. I.e. one access by the user may go through multiple interfaces. The plurality of interfaces may include, for example, interface 6, interface 7, interface 8, and interface 9. As shown in fig. 3, there are 10 ten thousand QPS request interfaces 6, but there are 50 thousand QPS request interfaces 7, i.e. the request size of interface 2 exceeds the request size of interface 1. For example, using the example of the usage behavior of the user of the a application program to grab the red packet, 10 ten thousand QPS requests the red packet ID, and 50 ten thousand QPS users hold the red packet ID and divide the red packet, where the user behavior of the red packet is a typical second killing activity, which may be a user request path of a non-funnel traffic model.
Since the request for the next interface is not simply amplified repeatedly for the previous interface in the non-funnel model, the amplified request cannot be guaranteed to have uniqueness. Therefore, the last interface cannot be simply and repeatedly amplified to obtain accurate model pressure measurement performance. In addition, in order to simulate the real behavior of the user as much as possible, the interface with large subsequent request flow has data when the interface with small previous request flow uses the interface with small previous request flow, and the data should be continuously used when the interface with small previous request flow generates the data, for example, as shown in fig. 3, the interface 1 may first spend some time generating a batch of data for the interface 2 to use, and then the interface 2 generates the data while the interface 1 still generates the data when using the data generated by the interface 1. Because the corresponding request quantity of each interface in the non-funnel model is not necessarily smaller than the request quantity of the previous interface, the accuracy of determining the model pressure measurement performance of the non-funnel model is low.
The present application will be described in detail with reference to specific examples.
In a first embodiment, as shown in fig. 4, fig. 4 shows a flowchart of a model pressure measurement performance determination method provided in the embodiment of the present application, which may be implemented by a computer program and may be run on a device including an application program. The computer program may be integrated into the application or may run as a separate tool-like application.
Specifically, the method for determining the pressure measurement performance of the model comprises the following steps:
s101, acquiring a first use case and a second use case in a non-funnel model;
according to some embodiments, the execution subject of the embodiments of the present application may be, for example, a server. The server is not specific to a fixed server. For example, the server may be a server cluster formed by a plurality of servers according to actual needs, or may be a server determined based on an application scenario of a non-funnel model.
The model pressure measurement performance determination method of the present application can be applied to determination of non-funnel model performance, for example. The non-funnel model is not specific to a fixed non-funnel model. For example, when the application of the non-funnel model changes, the non-funnel model also changes accordingly. For example, when the number of interfaces included in the non-funnel model changes, the non-funnel model may also change accordingly.
It is readily understood that the first use case and the second use case belong to the same interface. The first and second use cases may be, for example, two use cases obtained by dividing a certain interface.
Optionally, the first example only refers to a use case executed first after the interface is split, and the first example does not refer to a certain fixed use case in particular. For example, when an interface changes, the first use case obtained by dividing the interface also changes correspondingly.
In some embodiments, the second case refers to only a use case that is executed after the first case starts to be executed after the interface is split, and the second case does not refer to a certain fixed use case in particular. For example, when an interface changes, the second use case obtained by dividing the interface also changes correspondingly.
According to some embodiments, when the server executes the model pressure measurement performance determination method, the server may obtain the first use case and the second use case in the non-funnel model.
S102, executing a first case, and acquiring a first data set corresponding to the first case; (ii) a
In some embodiments, a collection refers to a collection of concrete or abstract objects with certain properties. A data set is a collection of data having a certain characteristic. The first data set refers to a set composed of data acquired after the first case is executed. 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 include, for example, only input data input for the first use case, only output data acquired after the first use case is executed, or partial data in the input data and the output data.
It will be readily appreciated that the first set of data does not refer specifically to a fixed set. For example, when the type of data included in a first data set changes, the first data set also changes accordingly. For example, when the amount of data included in the first data set changes, the first data set also changes accordingly. For example, when the acquisition mode for the first data set changes, the first data set also changes accordingly.
According to some embodiments, when the server executes the model pressure measurement 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 instance and obtain a first set of data corresponding to the first instance after beginning execution of the first instance.
S103, importing the first data set into a second data set corresponding to a second example, and executing the second example;
in some embodiments, the second data set refers to a data set corresponding to the second use case. The second data set does not refer specifically to a data set. The second data set may include, for example, input data entered for a second use case. For example, when a first set of data changes, the second set of data changes accordingly. For example, when the acquisition mode for the second data set changes, the second data set also changes accordingly. For example, the second data set may be formed by only the first data set import or may be comprised of the first data set and only data entered for the second data set.
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. The server may perform the second use case when importing the first data set into a data set corresponding to the second use case.
It is readily understood that the second case begins to execute no earlier than the first case, i.e., the second case is executed after the first user begins execution. That is, the second use case starts to be executed after the first use case starts to be executed, that is, the time point of starting to execute the second use case is after the time point of starting to execute the first use case.
S104, acquiring a first execution result of the first use case and a second execution result of the second use case, and determining the pressure measurement performance of the non-funnel model based on the first execution result and the second execution result.
According to some embodiments, the first execution result refers to an execution result corresponding to the first instance, which is obtained by the server based on the first data set. The first execution result does not refer to a fixed result. For example, when the first data set changes, the first execution result also changes accordingly. For example, when the amount of data included in the first data set changes, the first execution result also changes accordingly.
In some embodiments, since 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, when the first data set includes only input data input for the first use case, the server may obtain a first execution result of the first use case after the server executes the first use case based on the first data set. When the first data set includes only output data acquired after execution of the first use case, the server may acquire the first execution result of the first use case directly based on the output data, for example.
In some embodiments, the second execution result refers to an execution result corresponding to the second use case. The second execution result does not refer to a fixed result. For example, when the first data set changes, the second data set also changes accordingly, and the server changes accordingly based on the second execution result of the second use case acquired by the second data set.
It is readily understood that pressure testing, i.e., pressure testing, is one method for determining the stability of a non-funnel model. The pressure measurement performance may be used, for example, to represent the ability of the non-funnel model to withstand the requested pressure. The pressure measurement performance does not refer to a certain fixed performance. For example, when the first execution result changes, the pressure measurement performance of the non-funnel model also changes correspondingly. For example, when the second execution result changes, the pressure measurement performance of the non-funnel model also changes correspondingly. For example, when the first execution result and the second execution result are changed, the pressure measurement performance of the non-funnel model is changed correspondingly.
Optionally, when the server executes the method for determining the pressure measurement performance of the model, the server may obtain the first use case and the second use case in the non-funnel model. When the server executes the model pressure measurement 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 instance and obtain a first set of data corresponding to the first instance after beginning execution of the first instance. 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. The server may perform the second use case when importing the first data set into a data set corresponding to the second use case. The server may obtain a first execution result of the first use case and a second execution result of the second use case, and the server may determine the pressure measurement performance of the non-funnel model based on the obtained first execution result and the obtained second execution result.
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, where the first use case and the second use case belong to a same interface, the first use case may be executed, 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, obtaining a first execution result of the first use case and a second execution result of the second use case, the accuracy of obtaining the execution result may be improved, and the time for starting execution of the second use case is not earlier than the time for starting execution of the first use case, the accuracy of obtaining the second execution result may be improved, the pressure measurement performance of the non-funnel model is determined based on the first execution result and the second execution result, and the situation that the execution result is inaccurate due to obtaining only the first execution result or the second execution result may be reduced, the accuracy of determining the model pressure measurement performance of the non-funnel model can be improved.
Referring to fig. 5, fig. 5 is a schematic flow chart illustrating a method for determining a pressure measurement performance of a model according to an embodiment of the present disclosure. Specifically, the method comprises the following steps:
s201, acquiring a first use case and a second use case in a non-funnel model;
the specific process is as described above, and is not described herein again.
In some embodiments, fig. 6 illustrates a scenario diagram of a model pressure measurement performance determination method according to an embodiment of the present application. As shown in fig. 6, the server may split the a interface into use case 1 and use case 2. Wherein, the case 1 and the case 2 have data export and import relations. The data may be, for example, context data. That is, the data corresponding to example 1 can be exported and imported into the data corresponding to example 2. Case 1 and case 2 may constitute one scenario. Parallel execution of multiple scenarios may form, for example, a batch job. Multiple use cases can exist in one scene, wherein no context data context flow dependency exists among the multiple use cases. When the server executes a plurality of use cases, the use cases include, but are not limited to, parallel execution or serial execution.
S202, acquiring data transmission information between the first case and the second case;
in some embodiments, the data transfer information is used to represent a data transfer between the first use case and the second use case. The data transmission information does not refer to a fixed transmission information. For example, when the data transmission time point of the first case or the second case changes, the data transmission information also changes accordingly.
According to some embodiments, when the server acquires the first use case and the second use case, the server may acquire data transmission information between the first use case and the second use case. For example, when the server acquires use case 1 and use case 2, the server may acquire data transmission information between use case 1 and use case 2.
If the server does not acquire 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 separated and distributed to different generators.
S203, if data transmission information between the first use case and the second use case is acquired, distributing the first use case and the second use case to the same transmitter;
according to some embodiments, when the server acquires the first use case and the second use case, the server may acquire 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 transmitter. The server distributes the first use case and the second use case to the same generator based on the data transmission information, so that the execution efficiency of the first use case and the second use case can be improved, and the determination efficiency of the pressure measurement performance of the model can be further improved. When the server distributes the first use case and the second use case to the same transmitter, that is, the server may control the same transmitter to execute the first use case and the second use case, for example, multiple pressure test cases may be executed in the same pressure test program.
S204, executing a first case, and acquiring a first data set corresponding to the first case;
the specific process is as described above, and is not described herein again.
According to some embodiments, when the server acquires the first data set corresponding to the first case, the server may execute the first case first, and after starting to execute the first case, the server may acquire, for example, input parameters input for the first case and acquire output parameters corresponding to the first case. The server can select the input parameters and the output parameters, obtain the target parameters corresponding to the first case, add the target parameters to the first data set, and select the input data and the output data by the server, so that the accuracy of data acquisition can be improved, the accuracy of acquisition of the first data set can be improved, and the accuracy of determination of the pressure measurement performance of the model can be improved. When the server acquires the first data set corresponding to the first case, the server may store the first data set.
In some embodiments, as shown in fig. 6, use case 1 may correspond to, for example, an interface with a small request amount in the non-funnel traffic model, and use case 2 may correspond to, for example, an interface with a large request amount in the non-funnel traffic model. The fields of the export storage of case 1 are id1, name1, response1_1 and response1_ 2, wherein id1 and name1 are partial input parameters (request parameters) of case 1, and response1_1 and response1_ 2 are partial output fields (response parameters) of case 1. The server may, for example, select from the stored id1, name1 and response1_1, response1_ 2, get the target parameters id1 and name1, and add id1 and name1 to the first data set.
Optionally, the target parameter is 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 refer to a fixed parameter. When the selection instruction received by the server changes, the target parameter also changes correspondingly. For example, when the input parameter or the output parameter changes, the target parameter also changes accordingly.
S205, acquiring execution data corresponding to the first data set;
according to some embodiments, the execution data refers to data corresponding to the first data set acquired when the server executes the first instance. The execution data does not refer to a certain fixed data. When the type of data included in the execution data changes, the execution data also changes accordingly. When the execution data changes corresponding to the acquisition mode or the acquisition time point, the execution data also changes accordingly.
In some embodiments, the server may obtain the execution data corresponding to the first set of data when the server obtains the first set of data corresponding to the first instance. The execution data includes, but is not limited to, an execution time period, a data amount, and the like.
S206, if the execution data meets the first execution condition, importing the first data set into a second data set corresponding to the second example, and executing the second example;
the specific process is as described above, and is not described herein again.
In some embodiments, the first execution condition refers to a condition corresponding to execution data indicating whether to import the first data set into a second data set corresponding to the second instance. The first execution condition does not refer to a fixed condition. The first execution condition may also change accordingly, for example, when the server retrieves the condition modifying instruction for the first execution condition. The condition modification instruction includes, but is not limited to, a user directly input at the server or a condition modification instruction transmitted to the server through the terminal.
Wherein, the terminal includes but is not limited to: wearable devices, handheld devices, personal computers, tablet computers, in-vehicle devices, smart phones, computing devices or other processing devices connected to a wireless modem, and the like. Terminals can be called different names in different networks, for example: a user equipment, an access server, a subscriber unit, a subscriber station, a Mobile station, a remote server, a Mobile device, a subscriber server, a wireless Communication device, a user agent or user equipment, a cellular telephone, a cordless telephone, a Personal Digital Assistant (PDA), a fifth Generation Mobile Communication Technology (5G) network, a fourth Generation Mobile Communication Technology (4G) network, a third Generation Mobile Communication Technology (3rd-Generation, 3G) network, or a terminal in a future evolution network, etc.
According to some embodiments, when the server acquires the execution data corresponding to the first data set, the server may detect a relationship between the execution data corresponding to the first data set and the first execution condition. If the server determines that the execution data meets 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.
According to some embodiments, the execution data is an execution duration. If the server execution data meets the first execution condition, the server may 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 may determine 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 smaller than the second request amount. If the server determines that the execution duration reaches the duration threshold, the server may determine to acquire the first data set, and import the first data set into a second data set corresponding to the second example. The server determines the first data set based on the execution duration, so that the accuracy of acquiring the first data set can be improved, the situation that the second case cannot be executed due to data in the first data set can be reduced, and the accuracy of determining the model pressure measurement performance can be improved.
In some embodiments, the execution duration refers to the duration of time that the server executes the first instance. The execution duration is a duration from a starting execution time point of the first use case to an execution duration acquisition time point of the server. The execution duration does not refer to a fixed duration. For example, when the execution time length acquisition time point is changed, the execution time length may also be changed accordingly.
It is easily understood that the time period threshold refers to a time period critical value corresponding to the execution time period. The duration threshold does not refer specifically to a fixed duration threshold. The duration threshold may be, for example, a duration threshold determined by the server to correspond to the execution duration based on the first request amount corresponding to the first case and the second request amount of the second case.
Optionally, the first request amount refers to the amount requested for the first case. The first request amount may be, for example, a QPS (Queries Per second) request amount. QPS is the number of queries per second that a server can respond to per second, and is a measure of how much traffic a particular query server processes within a specified time. The second requested amount refers to the amount requested for the second instance. Wherein the first request amount is smaller than the second request amount. The request received by the server may be, for example, a request initiated by the terminal based on the obtained request instruction for the application program. The request command received by the terminal may be, for example, a click request command, and an example schematic diagram of the terminal interface in this case may be as shown in fig. 7, for example.
In some embodiments, the first instance may be, for example, use case 1 and the second instance may be, for example, use case 2. The execution data is an execution duration. The first execution condition may be, for example, that the execution duration satisfies the duration threshold, i.e., the first execution condition may be, for example, that the execution duration is greater than or equal to the duration threshold. The server may acquire the first QPS request amount corresponding to the first instance as, for example, 50 ten thousand QPS requests, and acquire the second QPS request amount corresponding to the second instance as, for example, 100 ten thousand QPS requests. The duration threshold may be, for example, 120 seconds. When the server obtains the execution duration of 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 to obtain the first data set, and import the first data set into the second data set corresponding to the second example.
In some embodiments, the execution data may be, for example, an execution duration, and when the first data set of the server imports the second data set corresponding to the second instance and executes the second instance, 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 example.
It is easy to understand that the server obtains the first QPS request amount corresponding to the first instance may be, for example, 50 ten thousand QPS requests, and obtains the second QPS request amount corresponding to the second instance may be, for example, 100 ten thousand QPS requests. The duration threshold may be, for example, 120 seconds. When the server acquires that the execution duration is 120 seconds, that is, the server determines that the execution duration 120 seconds reaches the duration threshold 120 seconds, the server may start to execute the second example.
According to some embodiments, the execution data is a data volume, and the data volume corresponding to the first data set may be obtained when the first data set is imported into the second data set corresponding to the second instance if the server execution data satisfies the first execution condition. If the data volume reaches the data volume threshold, the server may determine to acquire the first data set, and import the first data set into a second data set corresponding to the second use case. The server determines the first data set based on the data volume, so that the accuracy of acquiring the first data set can be improved, the situation that the second use case cannot be executed due to data included in the first data set can be reduced, and the accuracy of determining the model pressure measurement performance can be improved.
In some embodiments, the amount of data is used to represent how much of the number is included in the first set of data. The amount of data does not refer to a certain fixed duration. For example, when the execution duration of the first use case changes, the data size also changes accordingly. For example, when the execution efficiency of the first use case changes, the data amount also changes accordingly.
It is easily understood that the data amount threshold refers to a critical value corresponding to the data amount, and the data amount threshold does not refer to a fixed threshold. For example, for threshold setting instructions that different interface servers may retrieve. For example, when the request amount for the first or second use case changes, the data amount threshold may also change accordingly.
Optionally, the data size corresponding to the first data set acquired by the server may be, for example, 20.1 ten thousand data sizes. The data volume threshold may be, for example, a 20-thousand data volume. If the data volume of 20.1 ten thousand reaches the data volume threshold of 20 ten thousand, the server may determine to acquire the first data set, and import the first data set into a second data set corresponding to the second example.
In some embodiments, the execution data may be, for example, a data amount, and when the server imports the first data set into the second data set corresponding to the second example, and executes the second example, the server may determine whether the data amount corresponding to the first data set reaches a data amount threshold. If the server determines that the amount of data reaches the data amount threshold, the server may begin executing the second use case.
It is easy to understand that, when the server acquires the data volume corresponding to the first data set, the server may acquire the data volume once every preset time period, for example. The amount of data acquired by the server may be, for example, 20.1 ten thousand. The data volume threshold may be, for example, a 20-thousand data volume. If the data volume of 20.1 ten thousand reaches the data volume threshold of 20 ten thousand, the server may start to execute the second example.
According to some embodiments, when importing the first data set into the second data set corresponding to the second instance 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 instance if the execution data satisfies the first execution condition, and reset the execution data and retrieve the first data set. And if the newly acquired execution data meets a second execution condition, importing the newly acquired first data set into a second data set corresponding to the second use case. The server resets the execution data and reacquires the first data set, so that the reacquired first data set can be imported into the second data set in time, excessive data stored in the first data set is reduced, the first case export data can be imported into the second data set in time, the storage duration of the data is reduced, and the determination efficiency of the model pressure measurement performance can be improved.
In some embodiments, the first instance may be, for example, use case 1 and the second instance may be, for example, use case 2. The execution data is an execution duration. The first execution condition may be, for example, that the execution duration satisfies a duration threshold, that is, the first execution condition may be, for example, that the execution duration is greater than or equal to a duration threshold, and the duration threshold may be, for example, 120 seconds. The server may acquire the first QPS request amount corresponding to the first instance as, for example, 50 ten thousand QPS requests, and acquire the second QPS request amount corresponding to the second instance as, for example, 100 ten thousand QPS requests. When the server obtains the execution duration of 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 to obtain the first data set, and import the first data set into the second data set corresponding to the second example. After the server imports the first data set into the second data set corresponding to the second instance, the server may reset the execution duration and reacquire the execution duration and the first data set. The second execution condition may be, for example, that the execution duration satisfies a duration threshold, i.e., the second execution condition may be, for example, that the execution duration is greater than or equal to a duration threshold, which may be, for example, 120 seconds. When the execution duration re-acquired by the server is 120 seconds, that is, the server determines that the execution duration 120 seconds reaches the duration threshold 120 seconds, the server may determine to re-acquire the first data set, and re-import the first data set into the second data set corresponding to the second example.
In some embodiments, the second execution condition refers to a condition for judging the execution data after the data reset is executed. The second execution condition may be identical to the first execution condition or may not be identical to 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 120 seconds, for example, and the duration threshold corresponding to the second execution condition may also be 120 seconds, for example. For example, when the execution data is execution time, the time length threshold corresponding to the first execution condition may be, for example, 120 seconds, and the time length threshold corresponding to the second execution condition may be, for example, 140 seconds.
According to some embodiments, the number of imports of the first data set into the second data set corresponding to the second use case is at least one. If the first data set acquired by the server for the first time meets the set requirement, the number of times that the server imports the first data set into the second data set corresponding to the second example may be only one.
S207, a first execution result of the first use case and a second execution result of the second use case are obtained, and the pressure measurement performance of the non-funnel model is determined based on the first execution result and the second execution result.
The specific process is as described above, and is not described herein again.
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 may be distributed to the sender. For example, the server may control the H-blaster to execute the first case and obtain the first data set corresponding to the first case. When the server imports the first data set into the second data set, the H-shaped generator can be controlled 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 generator, the execution efficiency of the first use case and the second use case can be improved, and the determination efficiency of the model pressure measurement performance can be further improved.
Optionally, the server may obtain the first execution result and the second execution result at the same time, or obtain the first execution result and the second execution result at different time points.
It will be readily appreciated that after the server determines the pressure measurement performance of the non-funnel model, the server may apply the non-funnel model to the application, i.e., the server may provide services to users using the application based on the non-funnel model. Therefore, the server can be used for indicating the improvement of the performance of the non-funnel model, so that the stability of the non-funnel model is improved, and the use experience of a user is improved.
In one or more embodiments of the application, data transmission information between a first use case and a second use case is acquired by acquiring the first use case and the second use case in a non-funnel model, and if the data transmission information between the first use case and the second use case is acquired, the first use case and the second use case are distributed to the same generator, so that the execution efficiency of the first use case and the second use case can be improved, and the determination efficiency of the pressure measurement performance of the model can be further improved. Then, the first example is executed, the first data set corresponding to the first example is acquired, the execution data corresponding to the first data set can be acquired, the first data set is imported into the second data set corresponding to the second example when the execution data meets the first execution condition, the second example is executed, the server determines the first data set based on the execution data, the accuracy of acquiring the first data set can be improved, the situation that the second example cannot be executed due to the data in the first data set can be reduced, and the accuracy of determining the pressure measurement performance of the model can be improved. Finally, the second use case is executed after the first user starts executing, so that the accuracy of obtaining the second execution result can be improved, the situation that the obtaining of the execution result is inaccurate due to the fact that only the first execution result or the second execution result is obtained is reduced, and the accuracy of determining the model pressure measurement performance of the non-funnel model can be improved.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Please refer to fig. 8, which shows a schematic structural diagram of a model pressure measurement performance determination apparatus according to an embodiment of the present application. The model pressure measurement capability determination means may be implemented as all or part of the apparatus in software, hardware, or a combination of both. The model pressure measurement performance determination apparatus 800 includes a use case acquisition unit 801, a use case execution unit 802, and a performance determination unit 803, in which:
a use case obtaining unit 801, configured to obtain a first use case and a second use case in a non-funnel model, where the first use case and the second use case belong to a same interface;
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;
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;
the performance determining unit 803 is 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 pressure measurement performance of the non-funnel model based on the first execution result and the second execution result.
According to some embodiments, fig. 9 is a schematic structural diagram of a model pressure measurement performance determination apparatus provided in an embodiment of the present application. As shown in fig. 9, the use case execution unit 802 includes a data obtaining subunit 812 and a set importing subunit 822, and the use case execution unit 802 is configured to import the first data set into a second data set corresponding to the second use case, and includes:
a data obtaining subunit 812, configured to obtain execution data corresponding to the first data set;
a set importing subunit 822, 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.
According to some embodiments, the execution data is an execution duration, and the set importing subunit 822 is configured to, when the execution data satisfies the first execution condition, import the first data set into a second data set corresponding to the second instance, specifically:
acquiring the execution duration of a first case;
determining a duration threshold corresponding to the execution duration based on a first request quantity corresponding to the first case and a second request quantity of the second case, wherein the first request quantity is smaller than the second request quantity;
and if the execution duration reaches a duration threshold, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second use case.
According to some embodiments, the use case execution unit 902, when configured to execute the second use case, is specifically configured to:
and if the execution time length reaches the time length threshold value, starting to execute the second use case.
According to some embodiments, the execution data is a data volume, and the set importing subunit 822 is configured to, when the execution data satisfies the first execution condition, import the first data set into a second data set corresponding to the second instance, specifically:
acquiring a data volume corresponding to the first data set;
and if the data volume reaches the data volume threshold value, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second use case.
According to some embodiments, the set importing sub-unit 822 is configured to, when importing the first data set into the second data set corresponding to the second example if the execution data meets the first execution condition, specifically:
if the execution data meets the first execution condition, importing the first data set into a second data set corresponding to the second example, resetting the execution data and reacquiring the first data set;
and if the newly acquired execution data meets a second execution condition, importing the newly acquired first data set into a second data set corresponding to the second use case.
According to some embodiments, fig. 10 shows a schematic structural diagram of a model pressure measurement performance determination apparatus provided in an embodiment of the present application. As shown in fig. 10, the apparatus includes a use case distributing unit 804, where the use case distributing unit 804 is used before executing the first case;
acquiring data transmission information between a first use case and a second use case;
and if the data transmission information between the first use case and the second use case is acquired, distributing the first use case and the second use case to the same transmitter.
According to some embodiments, the use case execution unit 802 is configured to, when acquiring the first data set corresponding to the first case, specifically:
acquiring input parameters input aiming at a first case and acquiring output parameters of the first case;
selecting an input parameter and an output parameter to obtain a target parameter corresponding to the first case;
the target parameter is added to the first set of data.
It should be noted that, when the model pressure measurement performance determination apparatus provided in the foregoing embodiment executes the model pressure measurement performance determination method, only the division of the above functional modules is taken as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the above described functions. In addition, the model pressure measurement performance determination apparatus and the model pressure measurement performance determination method provided in the above embodiments belong to the same concept, and details of implementation processes thereof are referred to in the method embodiments, and are not described herein again.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
In one or more embodiments of the present application, the use case obtaining unit may obtain a first use case and a second use case in the non-funnel model, where the first use case and the second use case belong to a same interface, the use case executing unit may execute the first use case and obtain a first data set corresponding to the first use case, the use case executing unit may further import the first data set into a second data set corresponding to the second use case and execute the second use case, and may improve accuracy of obtaining an execution result, and a time when the second use case starts to be executed is not earlier than a time when the first use starts to be executed, and may improve accuracy of obtaining a second execution result, the performance determining unit may determine, based on the first execution result and the second execution result, a pressure measurement performance of the non-funnel model, and may reduce a situation where obtaining of an execution result is inaccurate due to obtaining only the first execution result or the second execution result, the accuracy of determining the model pressure measurement performance of the non-funnel model can be improved.
An embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method for determining a model pressure measurement performance according to the embodiment shown in fig. 4 to 7, and a specific execution process may refer to specific descriptions of the embodiment shown in fig. 4 to 7, which is not described herein again.
The present application further provides a computer program product, where at least one instruction is stored in the computer program product, and the at least one instruction is loaded by the processor and executes the method for determining the model pressure measurement performance according to the embodiment shown in fig. 4 to 7, where a specific execution process may refer to specific descriptions of the embodiment shown in fig. 4 to 7, and is not described herein again.
Please refer to fig. 11, which is a schematic structural diagram of a server according to an embodiment of the present disclosure. As shown in fig. 11, the server 1100 may include: at least one processor 1101, at least one network interface 1104, a user interface 1103, a memory 1105, at least one communication bus 1102.
Wherein a communication bus 1102 is used to enable connective communication between these components.
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, a wireless interface.
The network interface 1104 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface).
Processor 1101 may include one or more processing cores, among other things. The processor 1101 connects various portions throughout the server 1100 using various interfaces and lines to perform various functions of the server 1100 and process data by executing or performing instructions, programs, code sets, or instruction sets stored in the memory 1105 and invoking data stored in the memory 1105. Optionally, the processor 1101 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 1101 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 1101, but may be implemented by a single chip.
The Memory 1105 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 1105 includes non-transitory computer-readable storage media. The memory 1105 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 1105 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 1105 may alternatively be at least one storage device located remotely from the processor 1101. As shown in fig. 11, the memory 1105, which is a type of computer storage medium, may include an operating system, a network communication module, a user interface module, and an application program for model pressure measurement performance determination.
In the server 1100 shown in fig. 11, the user interface 1103 is mainly used as an interface for providing input for a user, and acquiring data input by the user; and the processor 1101 may be configured to invoke an application program for model pressure measurement capability determination stored in the memory 1105, and specifically perform the following operations:
acquiring 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 a first case and acquiring a first data set corresponding to the first case;
importing the first data set into a second data set corresponding to a second example, and executing the second example;
the time for starting execution of the second example is not earlier than the time for starting execution of the first example;
and acquiring a first execution result of the first use case and a second execution result of the second use case, and determining the pressure measurement performance of the non-funnel model based on the first execution result and the second execution result.
According to some embodiments, the processor 1101 is configured to, when importing the first data set into the second data set corresponding to the second usage case, specifically perform the following operations:
acquiring execution data corresponding to the first data set;
and if the execution data meets the first execution condition, importing the first data set into a second data set corresponding to the second use case.
According to some embodiments, the executing data is an executing duration, and the processor 1101 is configured to import the first data set into a second data set corresponding to the second example if the executing data satisfies the first executing condition, including:
acquiring the execution duration of a first case;
determining a duration threshold corresponding to the execution duration based on a first request quantity corresponding to the first case and a second request quantity of the second case, wherein the first request quantity is smaller than the second request quantity;
and if the execution duration reaches a duration threshold, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second use case.
According to some embodiments, when the processor 1101 is configured to execute the second use case, the following operations are specifically performed:
and if the execution time length reaches the time length threshold value, starting to execute the second use case.
According to some embodiments, the execution data is a data volume, and the processor 1101 is configured to specifically perform the following operations when importing the first data set into the second data set corresponding to the second example if the execution data satisfies the first execution condition:
acquiring a data volume corresponding to the first data set;
and if the data volume reaches the data volume threshold value, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second use case.
According to some embodiments, the processor 1101 is configured to perform the following operations when importing the first data set into the second data set corresponding to the second instance if the execution data satisfies the first execution condition:
if the execution data meets the first execution condition, importing the first data set into a second data set corresponding to the second example, resetting the execution data and reacquiring the first data set;
and if the newly acquired execution data meets a second execution condition, importing the newly acquired first data set into a second data set corresponding to the second use case.
According to some embodiments, before performing the first example, the processor 1101 is further configured to perform the following operations:
acquiring data transmission information between a first use case and a second use case;
and if the data transmission information between the first use case and the second use case is acquired, distributing the first use case and the second use case to the same transmitter.
According to some embodiments, the processor 1101 is configured to perform the following operations when acquiring the first data set corresponding to the first example:
acquiring input parameters input aiming at a first case and acquiring output parameters of the first case;
selecting an input parameter and an output parameter to obtain a target parameter corresponding to the first case;
the target parameter is added to the first set of data.
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, where the first use case and the second use case belong to a same interface, the first use case may be executed, 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, obtaining a first execution result of the first use case and a second execution result of the second use case, the accuracy of obtaining the execution result may be improved, and the time for starting execution of the second use case is not earlier than the time for starting execution of the first use case, the accuracy of obtaining the second execution result may be improved, the pressure measurement performance of the non-funnel model is determined based on the first execution result and the second execution result, and the situation that the execution result is inaccurate due to obtaining only the first execution result or the second execution result may be reduced, the accuracy of determining the model pressure measurement performance of the non-funnel model can be improved.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk including floppy disks, optical disks, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any one of the server state determination methods as set forth in the above method embodiments.
It is clear to a person skilled in the art that the solution of the present application can be implemented by means of software and/or hardware. The "unit" and "module" in this specification refer to software and/or hardware that can perform a specific function independently or in cooperation with other components, where the hardware may be, for example, a Field-ProgrammaBLE Gate Array (FPGA), an Integrated Circuit (IC), or the like.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some service interfaces, devices or units, and may be an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned memory comprises: various media capable of storing program codes, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program, which is stored in a computer-readable memory, and the memory may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
The above description is only an exemplary embodiment of the present application, and the scope of the present application is not limited thereto. That is, all equivalent changes and modifications made in accordance with the teachings of this application are intended to be included within the scope thereof. Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

Claims (10)

1. A method for determining the pressure measurement performance of a model is characterized by comprising the following steps:
acquiring 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 acquiring 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 time for starting execution of the second case is not earlier than the time for starting execution of the first case;
and acquiring a first execution result of the first use case and a second execution result of the second use case, and determining the pressure measurement performance of the non-funnel model based on the first execution result and the second execution result.
2. The method of claim 1, wherein importing the first data set into a second data set corresponding to the second use case comprises:
acquiring execution data corresponding to the first data set;
and if the execution data meets a first execution condition, importing the first data set into a second data set corresponding to the second use case.
3. The method according to claim 2, wherein the execution data is an 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 instance includes:
acquiring the execution duration of the first use case;
determining a time length threshold value corresponding to the execution time length based on a first request quantity corresponding to the first use case and a second request quantity of the second use case, wherein the first request quantity is smaller than the second request quantity;
and if the execution duration reaches the duration threshold, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second example.
4. The method of claim 3, wherein the executing the second use case comprises:
and if the execution duration reaches the duration threshold, starting to execute the second use case.
5. The method according to claim 2, wherein the executing data is a data volume, and if the executing data satisfies a first executing condition, importing the first data set into a second data set corresponding to the second instance comprises:
acquiring a data volume corresponding to the first data set;
and if the data volume reaches the data volume threshold value, determining to acquire the first data set, and importing the first data set into a second data set corresponding to the second use case.
6. The method of claim 2, wherein importing the first data set into a second data set corresponding to the second instance if the execution data satisfies a first execution condition comprises:
if the execution data meets a first execution condition, importing the first data set into a second data set corresponding to the second instance, resetting the execution data and reacquiring the first data set;
and if the newly acquired execution data meets a second execution condition, importing the newly acquired first data set into a second data set corresponding to the second use case.
7. A model pressure measurement performance determination apparatus, comprising:
the device comprises a use case acquisition unit, a processing unit and a processing unit, wherein the use case acquisition unit is used for acquiring a first use case and a second use case in a non-funnel model, and the first use case and the second use case belong to the same interface;
the case execution unit is used for executing the first case and acquiring a first data set corresponding to the first case;
the case execution unit is further used for importing the first data set into a second data set corresponding to the second case and executing the second case;
and the performance determining unit is used for acquiring a first execution result of the first use case and a second execution result of the second use case, and determining the pressure measurement performance of the non-funnel model based on the first execution result and the second execution result.
8. A server, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.
9. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-6.
10. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-6.
CN202111274717.1A 2021-10-29 2021-10-29 Model pressure measurement performance determination method and device, server and storage medium Pending CN114020617A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111274717.1A CN114020617A (en) 2021-10-29 2021-10-29 Model pressure measurement performance determination method and device, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111274717.1A CN114020617A (en) 2021-10-29 2021-10-29 Model pressure measurement performance determination method and device, server and storage medium

Publications (1)

Publication Number Publication Date
CN114020617A true CN114020617A (en) 2022-02-08

Family

ID=80059085

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111274717.1A Pending CN114020617A (en) 2021-10-29 2021-10-29 Model pressure measurement performance determination method and device, server and storage medium

Country Status (1)

Country Link
CN (1) CN114020617A (en)

Similar Documents

Publication Publication Date Title
CN108647089B (en) Resource allocation method, device, terminal and storage medium
US10936371B2 (en) Method for resource allocation and related products
CN109542614B (en) Resource allocation method, device, terminal and storage medium
CN110333947B (en) Method, device, equipment and medium for loading subcontracting resources of game application
WO2017185616A1 (en) File storage method and electronic equipment
CN110222288B (en) Page display method, device and storage medium
CN106790525A (en) A kind of document down loading method and device
CN109688183A (en) Group control device recognition methods, device, equipment and computer readable storage medium
CN113204451A (en) Pressure testing method and system for Redis cluster, storage medium and terminal
CN110888658B (en) Method and device for dynamically changing function modules in application program and storage medium
CN111104178A (en) Dynamic library loading method, terminal device and storage medium
CN113191114B (en) Method and apparatus for validating a system
CN104462116B (en) Data selection method and device
CN114020617A (en) Model pressure measurement performance determination method and device, server and storage medium
CN108418730B (en) Network flow testing method, device, equipment and computer readable storage medium
CN110851327A (en) Hardware state information acquisition method and device, terminal and readable storage medium
CN110771113B (en) Brushing amount terminal detection method and device
CN108632054B (en) Information transmission quantity prediction method and device
CN114546171A (en) Data distribution method, data distribution device, storage medium and electronic equipment
CN112765019B (en) Pressure measurement method and device, storage medium and electronic equipment
CN114490374A (en) Applied pressure test method, electronic device, storage medium, and program product
CN114884990A (en) Screen projection method and device based on virtual screen
CN111818509B (en) Resource conversion method, device and equipment
CN110231896B (en) Information sending method and device, electronic equipment and storage medium
CN112965767A (en) Job processing method and apparatus, electronic device, and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination