CN111143209B - Layering pressure testing method and device, electronic equipment and storage medium - Google Patents
Layering pressure testing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111143209B CN111143209B CN201911340717.XA CN201911340717A CN111143209B CN 111143209 B CN111143209 B CN 111143209B CN 201911340717 A CN201911340717 A CN 201911340717A CN 111143209 B CN111143209 B CN 111143209B
- Authority
- CN
- China
- Prior art keywords
- layer
- service
- target
- sub
- tested
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
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)
- Monitoring And Testing Of Exchanges (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a layering pressure testing method, a layering pressure testing device, electronic equipment and a storage medium, wherein the layering pressure testing method comprises the steps of firstly determining target data quantity of each sub-layer to be tested according to a target inlet QPS value; determining target traffic of the layering pressure test process; then, according to the calling relation reverse sequence among all the sub-layers to be tested, sequentially testing all the sub-layers to be tested by using the target traffic volume to obtain the real data volume corresponding to all the sub-layers to be tested; and finally, comparing the real data volume corresponding to each sub-layer to be tested with the target data volume corresponding to the sub-layer to be tested to obtain the test result of each sub-layer to be tested. The method has the advantages that the division of the sub-layers of the code realization layer is realized, the pressure test is carried out on each sub-layer, the test result of each sub-layer is finally obtained, and the test result is analyzed, so that the specific sub-layer with the performance problem can be judged, and the positioning of the performance problem is more accurate.
Description
Technical Field
The present invention relates to the field of software development technologies, and in particular, to a hierarchical pressure testing method and apparatus, an electronic device, and a storage medium.
Background
Pressure testing refers to the situation in which the code implementation layer running the software product is tested for the flow pressure value that the software product can withstand during the development of the software product. And a developer can analyze the performance problem of the code realization layer by using the test result of the pressure test, and further adopts corresponding means to optimize the code realization layer or adjust the structure.
At present, when a pressure test is performed on a code implementation layer in a Web (World Wide Web) architecture, information such as the amount of page browsing, the number of independent visitors of a website and the like which can be achieved is estimated on one side of a software product, then the possible bearing pressure of an interface called by the code implementation layer is estimated according to the information, further a QPS (query rate per second) value of the code implementation layer is estimated, finally a real QPS value is obtained through a specific pressure test process, and whether the performance of the code implementation layer accords with pressure bearing expectation is confirmed by judging whether the real QPS value is equal to the estimated QPS value.
However, current Web architecture structures are often very complex, and the code implementation layer is often further divided into several sub-layers, such as front-end page layer, front-end logic implementation middle layer, business layer, service layer, data layer, and so on. The conventional method for carrying out pressure test on the code implementation layer can only know whether the overall performance of the code implementation layer meets the pressure bearing expectation or not in a macroscopic manner, the pressure bearing relation between all the sub-layers in the code implementation layer cannot be defined, and when the performance of the code implementation layer does not meet the pressure bearing expectation, the specific sub-layer of the performance problem which causes the code implementation layer to not meet the pressure bearing expectation cannot be determined.
Disclosure of Invention
The invention provides a layered pressure testing method, a layered pressure testing device, electronic equipment and a storage medium, which are used for solving the problem that whether the performance of the whole code implementation layer can meet the pressure bearing expectation or not can only be known macroscopically by the existing pressure testing method.
In a first aspect, the present invention provides a method for testing stratified pressure, comprising:
acquiring a target entry QPS value;
determining the target data volume of each sub-layer to be tested according to the calling relation among the sub-layers to be tested in the code realization layer and the target entry QPS value;
determining the target traffic of the layering pressure testing process according to the target data of the last sub-layer to be tested in the code realization layer;
according to the reverse order of the calling relation among all the sub-layers to be tested, sequentially testing all the sub-layers to be tested by using the target traffic volume to obtain the real data volume corresponding to all the sub-layers to be tested;
and comparing the real data volume corresponding to each sub-layer to be tested with the target data volume corresponding to the sub-layer to be tested to obtain the test result of each sub-layer to be tested.
With reference to the first aspect, in an implementation manner of the first aspect, the target data amount of the sub-layer to be tested includes:
The method comprises the steps of enabling a target QPS value born by each service interface in a service layer, a target QPS value born by each service interface in a service layer and target times respectively called by each service interface in a data layer, wherein the service layer, the service layer and the data layer are sub-layers to be tested in the code implementation layer in sequence.
With reference to the first aspect, in an implementation manner of the first aspect, the step of determining, according to a call relationship between each sub-layer to be tested in the code implementation layer and the target entry QPS value, a target data amount of each sub-layer to be tested includes:
distributing the target inlet QPS value to each service interface according to the invoked proportion of each service interface of the service layer in the service scene, and obtaining the target QPS value born by each service interface;
distributing the target QPS value born by each service interface to each service interface according to the number of times that each service interface of the service layer is called by each service interface of the service layer, and obtaining the target QPS value born by each service interface;
and acquiring target times of data services in a data layer, which are respectively called by each service interface of the service layer.
With reference to the first aspect, in an implementation manner of the first aspect, the step of determining, according to the target data volume of the last sub-layer to be tested in the code implementation layer, the target traffic volume of the layered pressure test procedure includes:
and analyzing and obtaining target traffic of the layering pressure testing process according to target times of the data service in the data layer respectively called by each service interface, wherein the target traffic is used for representing the number of software product services containing one or more data services in the service scene.
With reference to the first aspect, in an implementation manner of the first aspect, the step of sequentially testing each sub-layer to be tested by using the target traffic according to the reverse order of the calling relationship between each sub-layer to be tested, and obtaining the real data volume corresponding to each sub-layer to be tested includes:
testing the data layer by utilizing the target traffic to obtain the real times of the data service in the data layer, which are respectively called by each service interface of the service layer;
according to the real times of each service interface in the service layer for calling the data service and the target traffic, calculating the real QPS value born by each service interface in the service layer;
And calculating the true QPS value born by each service interface in the service layer according to the true QPS value born by each service interface in the service layer and the true times of each service interface called by the service interface in the service layer.
With reference to the first aspect, in an implementation manner of the first aspect, after the testing is performed on each sub-layer to be tested in turn by using the target traffic according to the reverse order of the calling relationship between each sub-layer to be tested, after obtaining the real data amount corresponding to each sub-layer to be tested, the method further includes:
acquiring response time of the data layer, response time of the service layer and response time of the service layer in the test process;
if the response time of the data layer is greater than or equal to the response time of the service layer, the target traffic is re-obtained;
and if the response time of the service layer is greater than or equal to the response time of the service layer, re-carding the calling relation among all the sub-layers to be tested.
With reference to the first aspect, in an implementation manner of the first aspect, after the testing is performed on each sub-layer to be tested in turn by using the target traffic according to the reverse order of the calling relationship between each sub-layer to be tested, after obtaining the real data amount corresponding to each sub-layer to be tested, the method further includes:
Acquiring an access flow threshold of the data layer;
and if the target traffic volume of accessing the data service in the data layer exceeds the access flow threshold during the test, the target traffic volume is recovered.
With reference to the first aspect, in an implementation manner of the first aspect, after the obtaining a target entry QPS value, the method further includes:
and carding calling relations among all sub-layers to be tested in the code realization layer according to the service scene.
With reference to the first aspect, in an implementation manner of the first aspect, the step of obtaining the test result of each sub-layer to be tested includes:
and according to the test result, analyzing whether the performance of each sub-layer to be tested in the code realization layer can reach the operation performance index of the software product.
In a second aspect, the present invention provides a layered pressure testing apparatus comprising:
the target QPS acquisition module is used for acquiring a target entry QPS value;
the target data volume determining module is used for determining the target data volume of each sub-layer to be tested according to the calling relation among the sub-layers to be tested in the code realization layer and the target entry QPS value;
The target traffic determining module is used for determining the target traffic of the layering pressure testing process according to the target data of the last sub-layer to be tested in the code realizing layer;
the testing module is used for testing each sub-layer to be tested in turn by using the target traffic according to the reverse order of the calling relation among the sub-layers to be tested, and obtaining the real data quantity corresponding to each sub-layer to be tested;
and the comparison module is used for comparing the real data volume corresponding to each sub-layer to be tested with the target data volume corresponding to the sub-layer to be tested to obtain the test result of each sub-layer to be tested.
With reference to the second aspect, in an implementation manner of the second aspect, the target data volume of the sub-layer to be tested includes:
the method comprises the steps of enabling a target QPS value born by each service interface in a service layer, a target QPS value born by each service interface in a service layer and target times respectively called by each service interface in a data layer, wherein the service layer, the service layer and the data layer are sub-layers to be tested in the code implementation layer in sequence.
With reference to the second aspect, in an implementation manner of the second aspect, the target data volume determining module includes:
The first target QPS acquisition unit is used for distributing the target inlet QPS value to each service interface according to the invoked proportion of each service interface of the service layer in the service scene to obtain the target QPS value born by each service interface;
the second target QPS acquisition unit is used for distributing the target QPS value born by each service interface to each service interface according to the number of times that each service interface of the service layer is called by each service interface of the service layer, so as to acquire the target QPS value born by each service interface;
the target calling number acquisition unit is used for acquiring target numbers of times that the data service in the data layer is respectively called by each service interface of the service layer.
With reference to the second aspect, in an implementation manner of the second aspect, the target traffic determining module is further configured to: and analyzing and obtaining target traffic of the layering pressure testing process according to target times of the data service in the data layer respectively called by each service interface, wherein the target traffic is used for representing the number of software product services containing one or more data services in the service scene.
With reference to the second aspect, in an implementation manner of the second aspect, the test module includes:
The real calling number acquisition unit is used for testing the data layer by utilizing the target traffic volume to acquire the real number of times that the data service in the data layer is respectively called by each service interface of the service layer;
the first real QPS acquisition unit is used for calculating the real QPS value born by each service interface in the service layer according to the real times of each service interface in the service layer for calling the data service and the target traffic;
the second real QPS obtaining unit is configured to calculate a real QPS value born by each service interface in the service layer according to a real QPS value born by each service interface in the service layer and a real number of times each service interface is called by a service interface in the service layer.
With reference to the second aspect, in an implementation manner of the second aspect, the method further includes:
the response time acquisition module is used for acquiring the response time of the data layer, the response time of the service layer and the response time of the service layer in the test process;
a response time comparison module, configured to retrieve the target traffic if the response time of the data layer is greater than or equal to the response time of the service layer; and if the response time of the service layer is greater than or equal to the response time of the service layer, re-carding the calling relation among all the sub-layers to be tested.
With reference to the second aspect, in an implementation manner of the second aspect, the method further includes:
the threshold value acquisition module is used for acquiring an access flow threshold value of the data layer;
and the flow comparison module is used for re-acquiring the target traffic volume of the data service in the data layer if the target traffic volume exceeds the access flow threshold value in the test process.
With reference to the second aspect, in an implementation manner of the second aspect, the method further includes:
and the carding module is used for carding the calling relation among all the sub-layers to be tested in the code realization layer according to the service scene.
With reference to the second aspect, in an implementation manner of the second aspect, the comparing module is further configured to: and according to the test result, analyzing whether the performance of each sub-layer to be tested in the code realization layer can reach the operation performance index of the software product.
In a third aspect, the present invention provides an electronic device, a memory for storing program instructions;
and the processor is used for calling and executing the program instructions in the memory so as to realize the layering pressure testing method of the first aspect.
In a fourth aspect, the present invention also provides a storage medium having a computer program stored therein, which when executed by at least one processor of a layered pressure testing apparatus performs the layered pressure testing method of the first aspect.
According to the technical scheme, the invention provides a layered pressure testing method, a layered pressure testing device, electronic equipment and a storage medium, the target data volume of each sub-layer to be tested is determined according to the calling relation between all sub-layers to be tested in a code implementation layer and the target QPS value of the entrance of the code implementation layer, then the target traffic volume of the layered pressure testing process is determined according to the target data volume of the last sub-layer to be tested in the code implementation layer, then the sub-layers to be tested are tested in turn according to the calling relation between all sub-layers to be tested, the real data volume corresponding to each sub-layer to be tested is obtained, finally the real data volume corresponding to each sub-layer to be tested is compared with the corresponding target data volume, and the testing result of each sub-layer to be tested is obtained. The invention can realize the division of specific sublayers of the code realization layer, and the pressure test is realized to each sublayer, and finally the test result of each sublayer is obtained and analyzed, so that the specific sublayer which has the performance problem can be judged, and the positioning of the performance problem is more accurate.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings that are needed in the embodiments will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a flow chart of a method for testing stratified pressure according to an embodiment of the present invention;
FIG. 2 is a flowchart of determining a target data amount of each sub-layer to be tested according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a specific structure of a code implementation layer according to an embodiment of the present invention;
fig. 4 is a flowchart of obtaining real data amounts corresponding to each sub-layer to be tested according to an embodiment of the present invention;
FIG. 5 is a flow chart of a second method for testing stratified pressure according to an embodiment of the present invention;
FIG. 6 is a flow chart of a third method for testing stratified pressure according to an embodiment of the present invention;
FIG. 7 is a block diagram of a layered pressure testing apparatus according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.
Detailed Description
At present, for the pressure test mode of the code implementation layer, only whether the overall performance of the code implementation layer can meet the pressure bearing expectation or not can be known macroscopically, but the pressure bearing relation between all the sub-layers in the code implementation layer cannot be clarified.
Fig. 1 is a flowchart of a method for testing a delamination pressure according to an embodiment of the present invention. As shown in fig. 1, the layering pressure testing method provided by the embodiment of the invention includes:
s101, acquiring a target entry QPS value.
In order to ensure that the situation that a resource loading error, overtime or loading is not achieved as much as possible when the software product is formally put on a shelf for use is guaranteed, in the pressure test stage, a pushing situation of the software product and a use situation of the software product are estimated, and further the maximum flow which can be born by the code implementation layer when the software product is used, namely the limit flow, is estimated, and the limit flow is used as a target QPS (query rate per second) value at an entrance of the code implementation layer.
In addition, service scenes corresponding to software products for performing the layered pressure test are different, and in order to perform more detailed and comprehensive pressure test on each sub-layer to be tested in the code implementation layer, calling relations among all sub-layers to be tested in the code implementation layer of the software product are required to be combed according to the service scene corresponding to the specific software product.
S102, determining target data quantity of each sub-layer to be tested according to calling relation among the sub-layers to be tested in the code realization layer and the target entry QPS value. Specifically, the target data size of the sub-layer to be tested includes: the method comprises the steps of enabling a target QPS value born by each service interface in a service layer, a target QPS value born by each service interface in a service layer and target times respectively called by each service interface in a data layer, wherein the service layer, the service layer and the data layer are sub-layers to be tested in the code implementation layer in sequence.
In the embodiment of the invention, the code realization layer is specifically divided into a service layer, a service layer and a data layer, and the three sub-layers are respectively subjected to pressure test, wherein the calling relation pointed by the three sub-layers is that a service layer interface calls a service layer interface, and the service layer interface calls data layer data service, which can be specifically expressed as a service layer, a service layer and a data layer. According to specific business logic realized by the software product, firstly determining the target data volume which can be born by each business interface in the business layer, then further determining the target data volume which can be born by each service interface in the service layer according to the target data volume of each business interface in the business layer, and finally obtaining the target times of calling the data service in the data layer by each service interface, wherein the target times are the target data volume in the data layer.
S103, determining the target traffic volume of the layering pressure testing process according to the target data volume of the last sub-layer to be tested in the code realization layer. The step S103 specifically includes analyzing and obtaining a target traffic volume of the layered pressure testing process according to the target times of the data service in the data layer respectively called by each service interface, where the target traffic volume is used to represent the number of software product services containing one or more data services in the service scenario.
In the embodiment of the invention, the last sublayer to be tested of the code implementation layer is a data layer, the data layer can be understood as a database, a large number of data services are stored in the data layer to provide data support for software products, therefore, after the target data volume of each sublayer is determined, the target data volume in the data layer is estimated, the optimal data volume which can be called by the software products, namely, the target traffic volume, is determined, the target traffic volume is obtained through the specific condition that the data services in the data layer are called, and only the finally determined target traffic volume in the step is an expected limit value because the determined target entry QPS value and the target data volume of each level are all values of the limit under the ideal state. The number of data services in the embodiments of the present invention may also be understood as traffic.
And S104, testing each sub-layer to be tested in turn by using the target traffic according to the reverse order of the calling relation among the sub-layers to be tested, and obtaining the real data volume corresponding to each sub-layer to be tested.
In the embodiment of the invention, the calling relation among all sub-layers to be tested is business layer- & gt service layer- & gt data layer, and in the pressure test, the specific test sequence is data layer- & gt service layer- & gt business layer, the expected target business volume is input into the data layer, the number of times that the data service is actually called by the service interface in the data layer is tested, then the real flow value born by each interface of the service layer is calculated according to the real number of times that the data service is called, and finally the real flow value born by each interface of the service layer is calculated according to the real condition that each service interface in the service layer is called by each business interface in the service layer.
S105, comparing the real data volume corresponding to each sub-layer to be tested with the target data volume corresponding to the sub-layer to be tested, and obtaining the test result of each sub-layer to be tested.
The specific content of the test result of each sub-layer to be tested is: and according to the test result, analyzing whether the performance of each sub-layer to be tested in the code realization layer can reach the operation performance index of the software product.
According to the method and the device, through the pre-estimation of the previous stage and the pressure test of the later stage, the target data volume and the real data volume of each sub-layer to be tested are obtained successively, the target data volume and the real data volume of each sub-layer to be tested are compared, the relation between the target data volume and the real data volume can be judged, for example, the real data volume is equal to the target data volume or the real data volume is smaller than the target data volume, and if the real data volume is equal to the target data volume or the real data volume is smaller than the target data volume, the numerical value of the target data volume is within a certain threshold range, the fact that the sub-layer to be tested corresponding to the real data volume is not subjected to performance problems is indicated. Therefore, the method of the invention can carry out targeted pressure test on each sub-layer in the code realization layer, and position the performance problem to a specific sub-layer level, so that the positioning of the performance problem is more accurate.
Fig. 2 is a flowchart of determining a target data amount of each sub-layer to be tested according to an embodiment of the present invention. As shown in fig. 2, in the embodiment of the present invention, according to the call relationship between the sub-layers to be tested in the code implementation layer and the target entry QPS value, the step of determining the target data amount of each sub-layer to be tested includes:
S201, distributing the target entry QPS value to each service interface according to the invoked proportion of each service interface of the service layer in the service scene, and obtaining the target QPS value born by each service interface.
In the embodiment of the invention, according to the specific service scene of the tested software product, the ideal service interface calling proportion is estimated, for example, the calling proportion of the service interface 1 is 2%, the calling proportion of the service interface 2 is 5%, and the like, and the target inlet QPS value is X, so that the target QPS value born by the service interface 1 is 2%X, and the target QPS value born by the service interface 2 is 5%X.
S202, distributing the target QPS value born by each service interface to each service interface according to the number of times that each service interface of the service layer is called by each service interface of the service layer, and obtaining the target QPS value born by each service interface.
In the embodiment of the invention, one service interface in the service layer may be called by a plurality of service interfaces at the same time, and the number of times of calling may be more than one. For example, if the service interface 1 is called 1 time by the service interface 1 and the service interface 1 is called 3 times by the service interface 2, the calculated target QPS borne by the service interface 1 is 2%x+5%x 3.
S203, the target times that the data service in the data layer is respectively called by each service interface of the service layer are obtained.
For example, according to the service scenario of the software product in the embodiment of the present invention, an ideal data service call number may be determined, and in combination with the ideal pressure-bearing data of the service port, it may be estimated that the target number of times that the data service in the data layer is called by the service interface 1 is 1, the target number of times that the data service is called by the service interface 2 is 2, and so on.
Fig. 3 is a schematic diagram of a specific structure of a code implementation layer according to an embodiment of the present invention. In the embodiment of the present invention, the content of determining the target data amount of each sub-layer to be tested in the above embodiment may be described by taking the content in fig. 3 as a specific example, and specifically, as shown in fig. 3, the code implementation layer is sequentially divided into a service entry, a service layer and a data layer from bottom to bottom. Wherein, determining the target entry QPS value at the service entry as N, and estimating the processing according to the service sceneThe calling proportion of the wanted service interface is as follows: service interface WF 1 The proportion called is Z 1 % service interface WF 2 The proportion called is Z 2 % service interface WF n The proportion called is Z n In the ideal case,%, therefore, WF 1 The target QPS value is Z 1 ％*N，WF 2 The target QPS value is Z 2 ％*N，WF n The target QPS value is Z n N%; in the service layer, a service interface SCF 1 Quilt WF 1 Call X 1 Secondary, quilt WF 2 Call X 3 Secondary service interface SCF 2 Quilt WF 1 Call X 2 Secondary, quilt WF 2 Call X 4 Secondary service interface SCF n Quilt WF 2 Call X 5 Secondary, quilt WF n Call X n Then SCF can be obtained 1 The target QPS value is Z 1 ％*N*X 1 +Z 2 ％*N*X 3 ，SCF 2 The target QPS value is Z 1 ％*N*X 2 +Z 2 ％*N*X 4 ，SCF n The target QPS value is Z 2 ％*N*X 5 +Z n ％*N*X n The method comprises the steps of carrying out a first treatment on the surface of the In the data layer, the data services are SCF 1 The target number of calls is Y 1 Next, by SCF 2 The target number of calls is Y 2 Next, by SCF n The target number of calls is Y n And twice.
Therefore, in the embodiment of the invention, the target data volume in each sub-layer to be tested can be obtained in the limit flow state by using the service scene and the service logic used by the software product.
Fig. 4 is a flowchart of obtaining real data amounts corresponding to each sub-layer to be tested according to an embodiment of the present invention. As shown in fig. 4, in the embodiment of the present invention, according to the reverse order of the call relationship between the sub-layers to be tested, the steps of sequentially testing the sub-layers to be tested by using the target traffic to obtain the real data amount corresponding to the sub-layers to be tested include:
S301, testing the data layer by utilizing the target traffic volume, and obtaining the real times of the data service in the data layer, which are respectively called by each service interface of the service layer.
In the embodiment of the invention, the test is sequentially carried out according to the reverse order of the calling relation of each sub-layer in the code realization layer. Because the target traffic is the ideal limit traffic in the pressure test process, the actual pressure test is carried out on the code realization layer according to the traffic, so that the environment of the pressure test is ensured to be more close to the environment of the target in the pre-estimation process.
In addition, because a certain amount of data services are originally stored in the data layer, before the pressure test is performed by utilizing the target traffic, whether the traffic data in the target traffic is corresponding to the cached data in the data layer is also determined, if so, the traffic condition of the data in the cache should be considered in a specific calculation process, and the condition that the true times of the data layer are inaccurate due to repeated test and call of the same traffic data is avoided.
S302, according to the real times of each service interface in the service layer calling the data service and the target traffic, calculating the real QPS value born by each service interface in the service layer.
S303, calculating the true QPS value born by each service interface in the service layer according to the true QPS value born by each service interface in the service layer and the true times of each service interface called by the service interface in the service layer.
The pressure test process of the software product is actually a simulation process of the actual use of the software product, and in the actual use of the software product, there may be a lot of unexpected situations in the estimation stage, for example, the service called by the business interface is not the service provided by the software product itself, for example, the applet or the link of the beauty group is called in the WeChat, but the applet of the beauty group is not the service provided by the WeChat itself. Since the pressure test on the software product is only performed for the service of the software product, the situation is likely to affect the calculation of the actual call times of the service interface, for example, the service interface 1 calls the service interface 0 and the service interface 1 respectively, but the service interface 0 is not an interface to be tested, and then the call times of the service interface 0 are likely to be calculated in the total call times of the service interface 1 during the actual calculation, so that the calculated actual pressure bearing value of the service interface 1 is different from the actual pressure bearing value of the service interface 1 which only calls the service interface 1. In order to avoid the situation, in the embodiment of the invention, when the pressure test is performed, the service interface specifically called by the service interface is also required to be checked, whether the service interface belongs to the service provided by the software product itself is judged, the service interface which does not belong to the software product to be tested is excluded from the pressure test plan, and an alarm is sent to the calling situation of the service interface to prompt the tester.
Fig. 5 is a flowchart of a second method for testing stratified pressure according to an embodiment of the present invention. As shown in fig. 5, in the embodiment of the present invention, after the testing is sequentially performed on each sub-layer to be tested according to the reverse order of the call relationship between each sub-layer to be tested by using the target traffic, the method further includes:
s401, acquiring response time of the data layer, response time of the service layer and response time of the service layer in the test process.
In the embodiment of the invention, the response time of each sub-layer to be tested is detected while the pressure test is carried out on each sub-layer to be tested of the code realization layer.
S402, if the response time of the data layer is greater than or equal to the response time of the service layer, the target traffic is recovered.
In the embodiment of the invention, because the interface of each sub-layer to be tested is called and the specific processing content of the sub-layers are different, the response time of each sub-layer to be tested is different, and under normal conditions, the response time of the data layer is smaller than the response time of the service layer, and the response time of the service layer is smaller than the response time of the service layer. In order to enable the result of the pressure test of the code service layer to be more accurate, in the embodiment of the invention, the response time of each sub-layer to be tested is compared, and the specific pressure test result of each sub-layer can be used as a final result under the condition that the response time requirement is met.
Specifically, the condition of the response time requirement is that the response time of the data layer is smaller than the response time of the service layer, and the response time of the service layer is smaller than the response time of the service layer; if the response time of the data layer does not meet the requirement, the actual bearing capacity of the data layer is not expected to be good, and the bearing capacity of the data layer needs to be estimated again to acquire the target traffic again; if the response time of the service layer does not meet the requirement, it is indicated that the call relationship between the service layer and the service layer is estimated to be incorrect, and therefore, the call relationship needs to be re-carded in the following step S403.
S403, if the response time of the service layer is greater than or equal to the response time of the service layer, the calling relation among all the sub-layers to be tested is re-carded.
Therefore, the layering pressure testing method can also detect the response time of each sub-layer to be tested of the code realization layer, and can obtain more accurate pressure testing results by combining specific pressure testing conditions of each sub-layer to be tested.
Fig. 6 is a flowchart of a third method for testing stratified pressure according to an embodiment of the present invention. As shown in fig. 6, in the embodiment of the present invention, after the testing is performed on each sub-layer to be tested in turn by using the target traffic according to the reverse order of the calling relationship between each sub-layer to be tested, the method further includes:
S501, obtaining an access flow threshold of the data layer.
In the embodiment of the invention, the access flow of the data layer is controlled, and the phenomena of overtime and blocking of calling data service caused by overlarge access to the data service in the data layer are avoided.
S502, if the target traffic of accessing the data service in the data layer exceeds the access flow threshold in the test process, the target traffic is obtained again.
In the embodiment of the invention, a corresponding access flow threshold is set for the data layer service corresponding to each software product, the threshold is set according to the functions, attributes and the like of the software product, and in the test process, if the target traffic of accessing the data layer data service exceeds the access flow threshold, the target traffic needs to be re-evaluated, so that the target traffic can reach the access requirement of the data layer.
According to the technical scheme, the invention provides a layering pressure testing method, the target data quantity of each sub-layer to be tested is determined according to the calling relation among the sub-layers to be tested in a code implementation layer and the target QPS value of the entrance of the code implementation layer, then the target traffic quantity of the layering pressure testing process is determined according to the target data quantity of the last sub-layer to be tested in the code implementation layer, then the sub-layers to be tested are tested in turn according to the calling relation among the sub-layers to be tested, the real data quantity corresponding to each sub-layer to be tested is obtained, finally the real data quantity corresponding to each sub-layer to be tested is compared with the corresponding target data quantity, and the testing result of each sub-layer to be tested is obtained. The invention can realize the division of specific sublayers of the code realization layer, and the pressure test is realized to each sublayer, and finally the test result of each sublayer is obtained and analyzed, so that the specific sublayer which has the performance problem can be judged, and the positioning of the performance problem is more accurate.
Fig. 7 is a block diagram of a layered pressure testing apparatus according to an embodiment of the present invention. As shown in fig. 7, a layered pressure testing apparatus provided in an embodiment of the present invention includes:
a target QPS acquisition module 71 for acquiring a target entry QPS value; a target data amount determining module 72, configured to determine a target data amount of each sub-layer to be tested according to a calling relationship between each sub-layer to be tested in the code implementation layer and the target entry QPS value; a target traffic determining module 73, configured to determine a target traffic of the layered pressure testing process according to a target data amount of a last sub-layer to be tested in the code implementation layer; the test module 74 is configured to sequentially test each sub-layer to be tested by using the target traffic according to the reverse order of the calling relationship between the sub-layers to be tested, so as to obtain a real data volume corresponding to each sub-layer to be tested; and the comparison module 75 is configured to compare the real data amount corresponding to each sub-layer to be tested with the target data amount corresponding to the real data amount to obtain the test result of each sub-layer to be tested.
Wherein, the target data volume of the sub-layer to be tested comprises:
the method comprises the steps of enabling a target QPS value born by each service interface in a service layer, a target QPS value born by each service interface in a service layer and target times respectively called by each service interface in a data layer, wherein the service layer, the service layer and the data layer are sub-layers to be tested in the code implementation layer in sequence.
The target data amount determining module includes: the first target QPS acquisition unit is used for distributing the target inlet QPS value to each service interface according to the invoked proportion of each service interface of the service layer in the service scene to obtain the target QPS value born by each service interface; the second target QPS acquisition unit is used for distributing the target QPS value born by each service interface to each service interface according to the number of times that each service interface of the service layer is called by each service interface of the service layer, so as to acquire the target QPS value born by each service interface; the target calling number acquisition unit is used for acquiring target numbers of times that the data service in the data layer is respectively called by each service interface of the service layer.
The target traffic determining module is further configured to: and analyzing and obtaining target traffic of the layering pressure testing process according to target times of the data service in the data layer respectively called by each service interface, wherein the target traffic is used for representing the number of software product services containing one or more data services in the service scene.
The test module comprises: the real calling number acquisition unit is used for testing the data layer by utilizing the target traffic volume to acquire the real number of times that the data service in the data layer is respectively called by each service interface of the service layer; the first real QPS acquisition unit is used for calculating the real QPS value born by each service interface in the service layer according to the real times of each service interface in the service layer for calling the data service and the target traffic; the second real QPS obtaining unit is configured to calculate a real QPS value born by each service interface in the service layer according to a real QPS value born by each service interface in the service layer and a real number of times each service interface is called by a service interface in the service layer.
The layering pressure testing device further includes: the response time acquisition module is used for acquiring the response time of the data layer, the response time of the service layer and the response time of the service layer in the test process; a response time comparison module, configured to retrieve the target traffic if the response time of the data layer is greater than or equal to the response time of the service layer; and if the response time of the service layer is greater than or equal to the response time of the service layer, re-carding the calling relation among all the sub-layers to be tested.
The layering pressure testing device further includes: the threshold value acquisition module is used for acquiring an access flow threshold value of the data layer; and the flow comparison module is used for re-acquiring the target traffic volume of the data service in the data layer if the target traffic volume exceeds the access flow threshold value in the test process.
The layering pressure testing device further includes: and the carding module is used for carding the calling relation among all the sub-layers to be tested in the code realization layer according to the service scene.
The comparison module is also used for: and according to the test result, analyzing whether the performance of each sub-layer to be tested in the code realization layer can reach the operation performance index of the software product.
Fig. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention. As shown in fig. 8, an electronic device provided in an embodiment of the present invention includes: a memory 81 for storing program instructions; and a processor 82 for calling and executing program instructions in the memory to implement the hierarchical pressure testing method described in the above embodiment.
In embodiments of the present invention, processor 82 and memory 81 may be connected by a bus or other means. The processor may be a general-purpose processor, such as a central processing unit, a digital signal processor, an application specific integrated circuit, or one or more integrated circuits configured to implement embodiments of the present invention. The memory may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, a hard disk, or a solid state disk.
The embodiment of the invention also provides a storage medium, wherein the storage medium stores a computer program, and when at least one processor of the layering pressure testing device executes the computer program, the layering pressure testing device executes the layering pressure testing method.
The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a random-access memory (random access memory, RAM), or the like.
It will be apparent to those skilled in the art that the techniques of embodiments of the present invention may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in essence or what contributes to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present invention.
The same or similar parts between the various embodiments in this specification are referred to each other. In particular, for the service building apparatus and the service loading apparatus embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description in the method embodiments for the matters.
The embodiments of the present invention described above do not limit the scope of the present invention.
Claims (16)
1. A method of testing a delamination pressure, comprising:
acquiring a target entry QPS value;
determining the target data volume of each sub-layer to be tested according to the calling relation among the sub-layers to be tested in the code realization layer and the target entry QPS value;
determining the target traffic of the layering pressure testing process according to the target data of the last sub-layer to be tested in the code realization layer;
according to the reverse order of the calling relation among all the sub-layers to be tested, sequentially testing all the sub-layers to be tested by using the target traffic volume to obtain the real data volume corresponding to all the sub-layers to be tested;
comparing the real data volume corresponding to each sub-layer to be tested with the target data volume corresponding to the sub-layer to be tested to obtain the test result of each sub-layer to be tested;
the step of determining the target data volume of each sub-layer to be tested according to the calling relation between each sub-layer to be tested in the code realization layer and the target entry QPS value comprises the following steps:
distributing the target inlet QPS value to each service interface according to the invoked proportion of each service interface of the service layer in the service scene, and obtaining the target QPS value born by each service interface;
Distributing the target QPS value born by each service interface to each service interface according to the number of times that each service interface of the service layer is called by each service interface of the service layer, and obtaining the target QPS value born by each service interface;
acquiring target times of data service in a data layer respectively called by each service interface of the service layer;
the step of testing each sub-layer to be tested sequentially by using the target traffic according to the reverse order of the calling relation among the sub-layers to be tested, and obtaining the real data volume corresponding to each sub-layer to be tested comprises the following steps:
testing the data layer by utilizing the target traffic to obtain the real times of the data service in the data layer, which are respectively called by each service interface of the service layer;
according to the real times of each service interface in the service layer for calling the data service and the target traffic, calculating the real QPS value born by each service interface in the service layer;
and calculating the true QPS value born by each service interface in the service layer according to the true QPS value born by each service interface in the service layer and the true times of each service interface called by the service interface in the service layer.
2. The method of claim 1, wherein the target data volume of the sub-layer to be tested comprises:
the method comprises the steps of enabling a target QPS value born by each service interface in a service layer, a target QPS value born by each service interface in a service layer and target times respectively called by each service interface in a data layer, wherein the service layer, the service layer and the data layer are sub-layers to be tested in the code implementation layer in sequence.
3. The method of claim 2, wherein the step of determining the target traffic volume for the hierarchical pressure testing process based on the target data volume for the last sub-layer to be tested in the code implementation layer comprises:
and analyzing and obtaining target traffic of the layering pressure testing process according to target times of the data service in the data layer respectively called by each service interface, wherein the target traffic is used for representing the number of software product services containing one or more data services in the service scene.
4. The method according to claim 2, wherein after the testing is sequentially performed on each sub-layer to be tested by using the target traffic according to the reverse order of the calling relationship between the sub-layers to be tested, obtaining the real data amount corresponding to each sub-layer to be tested, the method further comprises:
Acquiring response time of the data layer, response time of the service layer and response time of the service layer in the test process;
if the response time of the data layer is greater than or equal to the response time of the service layer, the target traffic is re-obtained;
and if the response time of the service layer is greater than or equal to the response time of the service layer, re-carding the calling relation among all the sub-layers to be tested.
5. The method according to claim 2, wherein after the testing is sequentially performed on each sub-layer to be tested by using the target traffic according to the reverse order of the calling relationship between the sub-layers to be tested, obtaining the real data amount corresponding to each sub-layer to be tested, the method further comprises:
acquiring an access flow threshold of the data layer;
and if the target traffic volume of accessing the data service in the data layer exceeds the access flow threshold during the test, the target traffic volume is recovered.
6. The method of claim 1, further comprising, after the obtaining the target entry QPS value:
and carding calling relations among all sub-layers to be tested in the code realization layer according to the service scene.
7. The method of claim 1, wherein the step of obtaining the test result of each sub-layer to be tested by comparing the real data amount corresponding to each sub-layer to be tested with the target data amount corresponding to each sub-layer to be tested comprises:
and according to the test result, analyzing whether the performance of each sub-layer to be tested in the code realization layer can reach the operation performance index of the software product.
8. A layered pressure testing apparatus, comprising:
the target QPS acquisition module is used for acquiring a target entry QPS value;
the target data volume determining module is used for determining the target data volume of each sub-layer to be tested according to the calling relation among the sub-layers to be tested in the code realization layer and the target entry QPS value;
the target traffic determining module is used for determining the target traffic of the layering pressure testing process according to the target data of the last sub-layer to be tested in the code realizing layer;
the testing module is used for testing each sub-layer to be tested in turn by using the target traffic according to the reverse order of the calling relation among the sub-layers to be tested, and obtaining the real data quantity corresponding to each sub-layer to be tested;
The comparison module is used for comparing the real data volume corresponding to each sub-layer to be tested with the target data volume corresponding to the sub-layer to be tested to obtain the test result of each sub-layer to be tested;
the target data amount determining module includes:
the first target QPS acquisition unit is used for distributing the target inlet QPS value to each service interface according to the invoked proportion of each service interface of the service layer in the service scene to obtain the target QPS value born by each service interface;
the second target QPS acquisition unit is used for distributing the target QPS value born by each service interface to each service interface according to the number of times that each service interface of the service layer is called by each service interface of the service layer, so as to acquire the target QPS value born by each service interface;
the target calling number acquisition unit is used for acquiring target numbers of times that the data service in the data layer is respectively called by each service interface of the service layer;
the test module comprises:
the real calling number acquisition unit is used for testing the data layer by utilizing the target traffic volume to acquire the real number of times that the data service in the data layer is respectively called by each service interface of the service layer;
The first real QPS acquisition unit is used for calculating the real QPS value born by each service interface in the service layer according to the real times of each service interface in the service layer for calling the data service and the target traffic;
the second real QPS obtaining unit is configured to calculate a real QPS value born by each service interface in the service layer according to a real QPS value born by each service interface in the service layer and a real number of times each service interface is called by a service interface in the service layer.
9. The apparatus of claim 8, wherein the target data volume of the sub-layer to be tested comprises:
the method comprises the steps of enabling a target QPS value born by each service interface in a service layer, a target QPS value born by each service interface in a service layer and target times respectively called by each service interface in a data layer, wherein the service layer, the service layer and the data layer are sub-layers to be tested in the code implementation layer in sequence.
10. The apparatus of claim 9, wherein the target traffic determination module is further configured to: and analyzing and obtaining target traffic of the layering pressure testing process according to target times of the data service in the data layer respectively called by each service interface, wherein the target traffic is used for representing the number of software product services containing one or more data services in the service scene.
11. The apparatus as recited in claim 9, further comprising:
the response time acquisition module is used for acquiring the response time of the data layer, the response time of the service layer and the response time of the service layer in the test process;
a response time comparison module, configured to retrieve the target traffic if the response time of the data layer is greater than or equal to the response time of the service layer; and if the response time of the service layer is greater than or equal to the response time of the service layer, re-carding the calling relation among all the sub-layers to be tested.
12. The apparatus as recited in claim 9, further comprising:
the threshold value acquisition module is used for acquiring an access flow threshold value of the data layer;
and the flow comparison module is used for re-acquiring the target traffic volume of the data service in the data layer if the target traffic volume exceeds the access flow threshold value in the test process.
13. The apparatus as recited in claim 8, further comprising:
and the carding module is used for carding the calling relation among all the sub-layers to be tested in the code realization layer according to the service scene.
14. The apparatus of claim 8, wherein the contrast module is further to: and according to the test result, analyzing whether the performance of each sub-layer to be tested in the code realization layer can reach the operation performance index of the software product.
15. An electronic device, comprising:
a memory for storing program instructions;
a processor for invoking and executing program instructions in the memory to implement the hierarchical pressure testing method of any of claims 1-7.
16. A storage medium having stored therein a computer program which, when executed by at least one processor of a layered pressure testing apparatus, performs the layered pressure testing method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911340717.XA CN111143209B (en) | 2019-12-23 | 2019-12-23 | Layering pressure testing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911340717.XA CN111143209B (en) | 2019-12-23 | 2019-12-23 | Layering pressure testing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111143209A CN111143209A (en) | 2020-05-12 |
| CN111143209B true CN111143209B (en) | 2023-10-17 |
Family
ID=70519476
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911340717.XA Active CN111143209B (en) | 2019-12-23 | 2019-12-23 | Layering pressure testing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143209B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111694748B (en) * | 2020-06-18 | 2023-06-30 | 行吟信息科技(武汉)有限公司 | Pressure testing method and device |
| CN117785717A (en) * | 2024-01-05 | 2024-03-29 | 合肥卓讯云网科技有限公司 | Method and system for testing log reporting performance based on layering test |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102195829A (en) * | 2010-03-19 | 2011-09-21 | 升东网络科技发展(上海)有限公司 | Universal pressure simulation system and control method thereof |
| CN104573984A (en) * | 2015-01-27 | 2015-04-29 | 国网四川省电力公司电力科学研究院 | B/S information system state partitioning method based on healthy tree |
| CN105959177A (en) * | 2016-04-26 | 2016-09-21 | 网易（杭州）网络有限公司 | Game server stress test script generation method and device |
| CN106294177A (en) * | 2016-08-22 | 2017-01-04 | 腾讯科技（深圳）有限公司 | The method for testing pressure of a kind of interface and test equipment |
| CN110262959A (en) * | 2019-05-09 | 2019-09-20 | 五八有限公司 | Underlying services method for testing pressure, device, electronic equipment and storage medium |
| CN110377503A (en) * | 2019-06-19 | 2019-10-25 | 平安银行股份有限公司 | Method for testing pressure, device, computer equipment and storage medium |
| CN110413533A (en) * | 2019-09-03 | 2019-11-05 | 江苏满运软件科技有限公司 | AB test method, system, equipment and storage medium |
| CN110532191A (en) * | 2019-09-05 | 2019-12-03 | 北京博睿宏远数据科技股份有限公司 | A kind of method for testing pressure, system and cluster |
| CN110581785A (en) * | 2018-06-11 | 2019-12-17 | 中国移动通信集团浙江有限公司 | reliability evaluation method and device |
-
2019
- 2019-12-23 CN CN201911340717.XA patent/CN111143209B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102195829A (en) * | 2010-03-19 | 2011-09-21 | 升东网络科技发展(上海)有限公司 | Universal pressure simulation system and control method thereof |
| CN104573984A (en) * | 2015-01-27 | 2015-04-29 | 国网四川省电力公司电力科学研究院 | B/S information system state partitioning method based on healthy tree |
| CN105959177A (en) * | 2016-04-26 | 2016-09-21 | 网易（杭州）网络有限公司 | Game server stress test script generation method and device |
| CN106294177A (en) * | 2016-08-22 | 2017-01-04 | 腾讯科技（深圳）有限公司 | The method for testing pressure of a kind of interface and test equipment |
| CN110581785A (en) * | 2018-06-11 | 2019-12-17 | 中国移动通信集团浙江有限公司 | reliability evaluation method and device |
| CN110262959A (en) * | 2019-05-09 | 2019-09-20 | 五八有限公司 | Underlying services method for testing pressure, device, electronic equipment and storage medium |
| CN110377503A (en) * | 2019-06-19 | 2019-10-25 | 平安银行股份有限公司 | Method for testing pressure, device, computer equipment and storage medium |
| CN110413533A (en) * | 2019-09-03 | 2019-11-05 | 江苏满运软件科技有限公司 | AB test method, system, equipment and storage medium |
| CN110532191A (en) * | 2019-09-05 | 2019-12-03 | 北京博睿宏远数据科技股份有限公司 | A kind of method for testing pressure, system and cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111143209A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111143209B (en) | Layering pressure testing method and device, electronic equipment and storage medium | |
| CN110457175B (en) | Service data processing method and device, electronic equipment and medium | |
| CN110287332B (en) | Method and device for selecting simulation model in cloud environment | |
| CN110262959B (en) | Bottom layer service pressure testing method and device, electronic equipment and storage medium | |
| CN113162923B (en) | User reliability evaluation method and device based on user behaviors and storage medium | |
| CN110647447A (en) | Abnormal instance detection method, apparatus, device and medium for distributed system | |
| CN110691118A (en) | Service selection method and device in micro-service cluster | |
| CN111858369A (en) | Memory monitoring method, device, equipment and storage medium | |
| CN109213965B (en) | System capacity prediction method, computer readable storage medium and terminal device | |
| CN111752481A (en) | Memory monitoring and service life prediction method and system based on SPD | |
| CN114064445A (en) | Test method, device, equipment and computer readable storage medium | |
| CN108961071B (en) | Method for automatically predicting combined service income and terminal equipment | |
| CN114138634B (en) | Test case selection method and device, computer equipment and storage medium | |
| CN115795928A (en) | Accelerated degradation test data processing method and device based on gamma process | |
| CN115190010A (en) | Distributed recommendation method and device based on software service dependency relationship | |
| CN113128390B (en) | Sampling inspection method, sampling inspection device, electronic equipment and storage medium | |
| CN114090204A (en) | Resource prediction method and device | |
| WO2021223214A1 (en) | Interface performance test method and apparatus, and server and computer-readable storage medium | |
| CN111274687B (en) | Component failure rate prediction method and device, computer equipment and storage medium | |
| CN112242959B (en) | Micro-service current-limiting control method, device, equipment and computer storage medium | |
| CN116938769B (en) | Flow anomaly detection method, electronic device, and computer-readable storage medium | |
| CN113676377B (en) | Online user number evaluation method, device, equipment and medium based on big data | |
| CN115878415A (en) | Cluster server intelligent fault prediction method, system, terminal and storage medium | |
| CN114594971A (en) | System update verification method and device, computer equipment and storage medium | |
| CN117649019A (en) | Service month income data prediction method, device, equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |