CN108574610B - Pressure testing method and device, electronic equipment and medium - Google Patents
Pressure testing method and device, electronic equipment and medium Download PDFInfo
- Publication number
- CN108574610B CN108574610B CN201810091852.4A CN201810091852A CN108574610B CN 108574610 B CN108574610 B CN 108574610B CN 201810091852 A CN201810091852 A CN 201810091852A CN 108574610 B CN108574610 B CN 108574610B
- Authority
- CN
- China
- Prior art keywords
- request
- requests
- current
- type
- hit
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
The embodiment of the invention provides a pressure testing method, a pressure testing device, electronic equipment and a medium, wherein the method comprises the following steps: and aiming at each concurrent thread, obtaining a request hit rate, determining a first quantity of the first type of requests and a second quantity of the second type of requests according to the request hit rate, and sending the generated requests to a server. Taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, taking a regenerated second-class request different from the generated requests as current second-class requests, and returning to execute the step of sending the requests to the server so as to enable the server to perform stress test. Compared with the prior art, the method and the device have the advantage that the hit rate can be adjusted only manually in the subsequent process more conveniently.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a pressure testing method and apparatus, an electronic device, and a medium.
Background
With the development of internet technology, internet service providers increasingly rely on servers to provide various network services. Since a server may malfunction during its operation, and the service provided by the server may be affected, it is necessary to perform a stress test on the server to determine whether the server can operate for a long time. The pressure test is the influence on the system performance caused by long-time continuous operation of the system under a certain load condition. Stress testing helps to ascertain whether the system under test can support performance requirements, expected load increases, and the like.
Currently, a pressure tester having wrk, smoku, and meter is generally used, and a server performs a pressure test to determine whether the server can work for a long time. The pressure test is carried out by adopting the following steps:
firstly, a plurality of threads are set at a sending end, each thread is used for simulating a client, and the hit rate reached by the number of the set threads is about a preset hit rate.
Secondly, each thread continuously sends a set number of requests to the server, and the server searches whether data corresponding to the requests exist in the memory after receiving the requests sent by the sending end; if yes, judging that the request is hit; if not, when the server judges that the preset hit rate is not reached, the server can also read the data corresponding to the request from the hard disk and store the data in the memory. In this state, the current request misses the server's memory, and when the server receives the request next time, the request may hit the server's memory. And repeating the operation in a set period to test whether the server can normally work in the set period, so that the preset hit rate can be achieved.
The hit rate is a ratio of the number of requests received by the server to the number of requests received by the server, the number of requests having data corresponding to the request stored in the memory of the server. In practical situations, in order to perform a stress test on a server, the server needs to maintain a certain number of read/write times, and only a request that misses a server memory will generate data read/write between a hard disk and a memory of the server. Therefore, the requests sent by the stress test tool to the server are not all hits, and a certain hit rate exists.
However, when the pressure testing tool in the prior art sends a request to the server, the sending end does not adjust the hit rate of the request, and the sending end only manually adjusts the number of threads according to the actual hit rate of the request after the sending of the request and the execution of the process of completing the pressure test once, thereby achieving the purpose of adjusting the hit rate. The sending end can send a plurality of requests through one thread, and the hit rate of the requests is difficult to be accurately adjusted by adjusting the number of the threads. Therefore, the prior art has the technical problem that the hit rate of the adjustment request is inconvenient.
Disclosure of Invention
Embodiments of the present invention provide a pressure testing method, apparatus, electronic device, and medium, so as to achieve the purpose of conveniently adjusting the hit rate of a request. The specific technical scheme is as follows:
in order to achieve the above object, in a first aspect, an embodiment of the present invention provides a pressure testing method applied to a transmitting end, where the method includes:
acquiring a preset request hit rate aiming at each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread;
determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread;
generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests;
sending the current first type request and the current second type request to a server;
taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and returning to the step of sending the current first type request and the current second type request to the server so as to enable the server to carry out stress test.
Optionally, the preset number is determined according to a preset hit request change rate, and the hit request change rate is determined according to the number of different requests and the first number in every two rounds of hit requests.
Optionally, the third number of current first-type requests includes:
the first type of request is randomly selected from a first number of current first type of requests, the difference between the first number and a preset number.
In a second aspect, an embodiment of the present invention provides a pressure testing method, which is applied to a server, and the method includes:
receiving a request sent by a sender, wherein the request comprises: the method comprises the steps that a first quantity of first-type requests and a second quantity of second-type requests are sent by a sending end, and a preset request hit rate is obtained for each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread; determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests; sending the current first type request and the current second type request to a server; taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; returning to execute the step of sending the current first type request and the current second type request to the server;
judging whether data corresponding to the request exists in the memory of the mobile terminal or not aiming at each request;
and if the data corresponding to the request does not exist in the memory of the mobile terminal, storing the data corresponding to the request into the memory.
Optionally, after the data corresponding to the request is stored in the memory, the method further includes:
calculating the hit rate of all received first-class requests according to the number of the received first-class requests and the number of the received all requests, wherein the first-class requests are sent by all threads, and all the requests comprise: the first type of request and the second type of request are sent by each thread.
In a third aspect, an embodiment of the present invention provides a pressure testing apparatus, which is applied to a sending end, and includes: an acquisition module, a first setting module, a generation module, a sending module, and a second setting module, wherein,
the device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a preset request hit rate aiming at each concurrent thread, and the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread;
the first setting module is used for determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread;
the generation module is used for generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests;
the sending module is used for sending the current first type request and the current second type request to the server;
the second setting module is used for taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and returning to the step of sending the current first type request and the current second type request to the server so as to enable the server to carry out stress test.
Optionally, the preset number is determined according to a preset hit request change rate, and the hit request change rate is determined according to the number of different requests and the first number in every two rounds of hit requests.
Optionally, the third number of current first-type requests includes:
the first type of request is randomly selected from a first number of current first type of requests, the difference between the first number and a preset number.
In a fourth aspect, an embodiment of the present invention provides a pressure test device, which is applied to a server, and includes: a receiving module, a judging module and a storage module, wherein,
a receiving module, configured to receive a request sent by a sending end, where the request includes: the method comprises the steps that a first quantity of first-type requests and a second quantity of second-type requests are sent by a sending end, and a preset request hit rate is obtained for each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread; determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests; sending the current first type request and the current second type request to a server; taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; returning to execute the step of sending the current first type request and the current second type request to the server;
the judging module is used for judging whether data corresponding to the request exists in the memory of the judging module aiming at each request;
and the storage module is used for storing the data corresponding to the request into the memory under the condition that the judgment result of the judgment module is negative.
Optionally, the apparatus further includes a calculating module, configured to calculate hit rates of all the received first type requests according to the number of all the received first type requests and the number of all the received requests, where the first type requests are sent by all the threads, and all the requests include: the first type of request and the second type of request are sent by each thread.
In a fifth aspect, an embodiment of the present invention provides an electronic device, including a memory and a processor;
a memory for storing a computer program;
and the processor is used for realizing the pressure testing method steps of the first aspect when executing the program stored in the memory.
In a sixth aspect, an embodiment of the present invention provides an electronic device, including a memory and a processor;
a memory for storing a computer program;
and the processor is used for realizing the pressure testing method steps of the second aspect when executing the program stored in the memory.
In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is caused to execute the pressure testing method of the first aspect.
In an eighth aspect, embodiments of the present invention further provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the pressure testing method of the first aspect.
In a ninth aspect, the present invention further provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium is run on a computer, the computer is caused to execute the pressure testing method of the second aspect.
In a tenth aspect, embodiments of the present invention also provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the pressure testing method of the second aspect.
According to the pressure testing method, the pressure testing device, the electronic equipment and the medium, the first quantity corresponding to the first type of requests and the second quantity corresponding to the second type of requests are determined according to the set hit rate, each thread sends various requests to the server according to the set quantity, and the first type of requests can continuously hit the cache of the server along with the continuous sending of the requests, so that the set hit rate is achieved. Of course, it is not necessary for any product or method of practicing the invention to achieve all of the above advantages at the same time.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
FIG. 1 is a schematic diagram of a prior art pressure test;
FIG. 2 is a schematic flow chart of a first pressure testing method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a request change of a first pressure testing method according to an embodiment of the present invention;
FIG. 4 is a schematic flow chart of a second pressure testing method according to an embodiment of the present invention;
FIG. 5 is a schematic flow chart of a third pressure testing method according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a first pressure testing apparatus according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a second pressure testing apparatus according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a third pressure testing apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of another electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
Fig. 1 is a schematic diagram illustrating a principle of a pressure test in the prior art, and as shown in fig. 1, when a server is subjected to a pressure test, first, 8 threads are set at a sending end 100: 301. 302, 303, ·, 308, each thread being used to emulate a sender.
Then, each thread continuously sends a set number of requests to the server 200, and after receiving the request sent by the sending end 100, the server 200 searches whether data corresponding to the request exists in the memory; if yes, judging that the request is hit; if not, the data corresponding to the request can be read from the hard disk and stored in the memory when the preset hit rate is judged not to be reached. In this state, the current request misses the memory of the server 200, and when the server 200 receives the request next time, the request may hit the memory of the server 200. The above operations are repeated in a set period to test whether the server 200 can normally operate in the set period. In practical situations, in order to perform stress test on the server 200, the server 200 needs to maintain a certain number of read/write times, and only a request that misses the memory of the server 200 will generate data read/write between the hard disk and the memory of the server. Therefore, the requests sent by the stress test tool to the server are not all hits, and a certain hit rate exists.
For example, taking thread 301 as an example, thread 301 sends 10 requests to the server, and server 200 receives 10 requests sent by thread 301. For each request, the server 200 queries whether data corresponding to the request exists in its memory, and if not, reads the data corresponding to the request from the hard disk and stores the read data in the memory. In general, a process in which the server 200 reads data from the hard disk once and stores the read data in the memory once may be referred to as a one-time read-write process. When a certain number of read/write times per second is ensured between the memory of the server 200 and the hard disk, pressure is generated on data exchange between the memory of the server and the hard disk, and whether the server 200 can meet application requirements under the set pressure can be tested. In practical applications, the server 200 may store some data, and a part of the request sent by the sender may hit the memory of the server 200. Therefore, in order to simulate the real situation, the request sent by the sending end has a certain hit rate. However, when the existing pressure testing tool sends a request to the server 200, the sending end 100 does not adjust the hit rate of the request, and the sending end 100 only manually adjusts the number of threads according to the actual hit rate of the request after the pressure testing process is completed once. Therefore, the technical problem that the hit rate of the adjustment request is inconvenient exists in the prior art.
In order to solve the problems in the prior art, embodiments of the present invention provide a pressure testing method and apparatus, an electronic device, and a medium.
First, a first pressure testing method provided by an embodiment of the present invention is described below. It should be noted that the first pressure testing method provided in the embodiment of the present invention is preferably applied to a sending end.
Fig. 2 is a schematic flow chart of a first pressure testing method provided in the embodiment of the present invention, and as shown in fig. 2, the method includes:
s201: and acquiring a preset request hit rate aiming at each concurrent thread.
The request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread.
For example, the sending end 100 obtains a predetermined request hit rate, and the obtained request hit rate may be 0.6. The preset request hit rate is 0.6, that is, each time the server 200 receives 10 requests sent by the sending end 100, the server 200 may search, in the memory, data corresponding to 6 of the requests, and may determine that the 6 requests hit the memory of the server 200. The memory of the server 200 may be a cache of the server 200 in general.
In practical applications, in order to simulate a situation where a large number of clients access the server 200, a plurality of threads are set on the transmitting side for simulating a plurality of clients. In general, the server 200 receives access requests from a plurality of clients at the same time, and thus sets a plurality of concurrent threads on the transmitting side. The number of the set concurrent threads may be hundreds, thousands or tens of thousands.
S202: determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; and taking the sum of the first number and the second number as the total number of the requests sent by the current thread.
In practical application, the thread sending requests are sent serially, and if the number of requests to be sent by the thread is large, a request sending queue is formed on the thread. There are many ways in which requests in the request issue queue may be arranged. If each thread sends a hit request first, the hit rate of the requests reaches a high value, which is not practical, and therefore, when the server 200 is stress tested, each thread sends multiple rounds of requests, and the number of the requests in each round is as small as possible. In general, each thread may be configured to send 13 requests per round, and when the round of request sending is completed, the next round of 13 requests is sent. Thereby avoiding the problems caused by the overlong request sending queue.
And determining each data as the data of the first round request sent by the thread. For example, the first number of first type requests A is X; the second number of requests B of the second type is Y.
The number of requests hit by the current thread is: x;
the total number of requests sent by the current thread is: x + Y;
and X/(X + Y) ═ 0.6.
For example, the first number corresponding to the first type of request may be calculated according to a product of a preset number of requests per round per thread and a hit rate. For example, if the preset number of requests sent by the current thread in one round is 10, the first number is 10 × 0.6 — 6, and the second number may be 4.
S203: a first number of first type requests is generated as current first type requests and a second number of second type requests is generated as current second type requests.
The transmitting end 100 generates two types of requests of corresponding quantity according to the first quantity X and the second quantity Y determined in step S202.
For example, a first number X of first type requests may be considered current first type requests; and taking a second quantity of Y second-class requests as current second-class requests.
It should be noted that the first type of request may be a login request, a data read request, a data write request, and the like, and the types of the first type of request and the second type of request are not limited in the embodiment of the present invention. In addition, the embodiments of the present invention do not limit the methods that can generate the first type of request and the second type of request, and any method that can generate the first type of request and the second type of request can achieve the purpose of the embodiments of the present invention.
It will be appreciated that the first category of requests described above is merely a sort made for ease of distinction. In practical applications, the first type of request may include two or more different types of requests, and it is only necessary to ensure that the first type of request can hit the memory of the server 200. For example, the first type of request may include one or a combination of a login request, a data deletion request, and a data write request. Similarly, the second type of request may include two or more different types of requests, and it is only necessary to ensure that the second type of request does not hit the memory of the server 200.
S204: and sending the current first-type request and the current second-type request to a server.
Illustratively, a first number X of current first type requests and a second number Y of current second type requests are sent to the server 200 as a first round of requests.
For each thread, a request-send queue is formed when the two types of requests are sent. It can be understood that the order of the two types of requests in the request sending queue may be a random order, or may also be an order obtained by sorting according to a preset rule, and the embodiment of the present invention does not limit the order of the two types of requests in the request sending queue.
It is understood that the memory of the server 200 may be initialized before the request transmitted by the transmitting end 100 is transmitted to the server 200. For example, the memory of the server 200 may be emptied, or the data corresponding to the first type request in this step may be stored. Data stored in the server memory includes, but is not limited to, pictures, text, video files, and the like.
S205: taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and returning to the step of sending the current first type request and the current second type request to the server so as to enable the server to carry out stress test.
Wherein the third quantity is a difference between the first quantity and the predetermined quantity. The preset number may be set by a technician based on experience.
In practice, the preset number may be equal to the second number, or may be smaller than the second number.
Alternatively, the predetermined number may be determined according to a predetermined hit request change rate, and the hit request change rate may be determined according to the number of different requests and the first number in each two rounds of hit requests.
In implementation, there are a preset number Z of different requests in each two round hit of requests. Specifically, a hit request change rate S ═ Z/(X + Z) may be defined. After the preset hit rate and the number of requests per round are determined, the value of the first quantity X is determined, and further, the value of the preset quantity Z may be determined according to the preset hit request change rate S. Illustratively, when the preset hit rate has a value of 0.6, the total number of requests sent per round is 20, and the preset hit data change rate S is 0.25, then the first number X is 12 and the preset number Z is 4; when the preset hit rate has a value of 0.6, the total number of requests sent per round is 20, and the preset hit data change rate S is 0.2, then the first number X is 12 and the preset number Z is 3.
FIG. 3 is a schematic diagram illustrating a request change of a first pressure testing method according to an embodiment of the present invention; as shown in FIG. 3, a preset number Z of second type requests B1 and a third number (X-Z) of first type requests A1 in the first round of requests are taken as the first type requests A2 of the second round. The difference between the second number and the preset number in the first round of requests (Y-Z) is the second type of requests, which can be regarded as the third type of requests C1 in the first round of requests. It should be noted that the third number (X-Z) of first-type requests a1 may be randomly selected from X first-type requests a1 in the first round of requests, may also be selected according to the transmission sequence, or may also be selected in reverse order according to the transmission sequence, and the embodiment of the present invention does not limit the method for selecting the third number (X-Z) of first-type requests a1 from X first-type requests in the first round of requests. It can be seen that different hit request change rates can be achieved by setting different preset number values to meet different service requirements.
The second number Y of requests of the second type are regenerated as current requests of the second type B2 and current requests of the third type C2. It should be noted that, both the current second type request B2 and the current third type request C2 are different from the requests already sent by all threads, for example, the resource identifiers, hash values, MD5 values, user IDs, user IP addresses, and the like corresponding to the requests may be different. Because the regenerated second type of request B2 and the third type of request C2 are different from the previously sent requests, these requests do not hit the server 200.
Then, a step of sending a first number X of requests of the first type a2, a preset number Z of requests of the second type B2, and a difference between the second number and the preset number (Y-Z) of requests of the third type C2 to the server 200 is performed.
In general, how many rounds of requests the sender 100 needs to send to the server can be adjusted according to actual needs.
In the prior art, after the first round of request sending is completed, the number of threads is manually adjusted according to the request hit rate. For example, if the current hit rate is higher than the set hit rate and most or all of the requests sent by thread 301 hit server 200, then thread 301 is manually turned off, thereby reducing the overall hit rate. Similarly, when the request hit rate is lower than the set hit rate, the partial threads may be turned off, and the above problem may also occur. Therefore, the prior art has the defect that the number of threads needs to be adjusted manually.
By applying the embodiment shown in fig. 2 of the present invention, the first number corresponding to the first type of request and the second number corresponding to the second type of request are determined according to the set hit rate, each thread sends various requests to the server according to the set number, and the first type of request can continuously hit the cache of the server along with the continuous sending of the requests, so as to achieve the set hit rate.
In addition, the impact of closing thread 301 on hit rate may have the following three cases: insufficient reduction in hit rate; just the hit rate adjustment; the hit rate is reduced too much below the set hit rate. Therefore, the prior art also has the defect that the request hit rate adjustment is not accurate enough.
Similarly, when the existing stress test tool is applied to stress test the server, because the number of requests sent by each thread is preset, when the request hit rate needs to be adjusted, the request hit rate can also be adjusted by setting whether the server caches data corresponding to the requests sent by the threads. For example, if a cache manner of a certain data is set to be not cached manually, when the server receives a request corresponding to the data, the request cannot hit the data in the memory of the server, thereby reducing the request hit rate. Similarly, if the request hit rate needs to be increased, only the data corresponding to the request needs to be added to the memory of the server 200. In the above adjustment method, the type of the data that does not need to be cached or needs to be cached needs to be set, for example, when the data corresponding to the request is a picture, the picture in the jpg format needs to be cached or does not need to be cached. Similar to manually adjusting the number of threads, each decrease or increase in the number of types of cache data results in a change in the number of requests that hit memory. However, since the adjustment method can only set a certain type of data cache or not, and the amount of the certain type of data is large and is not fixed, it is difficult for the adjustment method to accurately adjust the hit rate of the request.
By applying the embodiment shown in fig. 2 of the present invention, the request hit rate is preset, the number of requests used for performing the pressure test is calculated according to the request hit rate, and only the first type of request hits the server in each round of requests sent, so that the hit rate is relatively accurate when the embodiment of the present invention is applied to performing the pressure test.
In addition, due to network delay and other reasons, the time when the simultaneously arriving requests sent by the sending end 100 arrive at the server 200 may have a certain time difference, so that the actual hit rate may differ from the preset request hit rate, and the actual request hit rate may be closer to the preset request hit rate by reducing the number of the requests sent in each round as much as possible and setting the number of threads as much as possible.
Optionally, the third number of current first-type requests includes:
the first type of request is randomly selected from a first number of current first type of requests, the difference between the first number and a preset number.
For example, taking the second round of requests as an example, from the first-class requests sent in the first round, X-Z current first-class requests are randomly selected as a part of the third number of current first-class requests, that is, the first-class requests in the second round of requests.
By applying the embodiment of the invention, the error in the process of requesting selection can be eliminated through random selection.
In a second aspect, the embodiment of the present invention further provides a second pressure testing method. It should be noted that the second pressure testing method provided by the embodiment of the present invention is preferably applied to a server.
Fig. 4 is a schematic flow chart of a second pressure testing method provided in the embodiment of the present invention, and as shown in fig. 4, the method includes:
s401: a request sent by a sender is received.
Wherein the request comprises: the method comprises the steps that a first quantity of first-class requests and a second quantity of second-class requests are sent by a sending end, and a preset request hit rate is obtained for each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread; determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests; sending the current first type request and the current second type request to a server; taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and returning to execute the step of sending the current first-type request and the current second-type request to the server.
Illustratively, the server 200 receives multiple rounds of requests sent by a sending end, wherein each round of requests includes: x requests of the first type A, Y requests of the second type B.
It should be noted that the multiple rounds of requests sent by the sending end and received by the server 200 are all generated according to steps S201 to S205.
S402: and judging whether the data corresponding to the request exists in the memory of the mobile terminal or not aiming at each request, and if the data corresponding to the request does not exist in the memory of the mobile terminal, executing the step S403.
For example, the step is described by taking the request m as an example, after the server 200 receives the request m, data corresponding to the request m is searched in its memory, and if the data corresponding to the request m is not searched, it is described that the data corresponding to the request m does not exist in the memory of the server 200, so the determination result in the step S402 is yes.
In addition, when data corresponding to the request m exists in the memory of the server 200, it is determined that the request m hits the memory of the server.
S403: and storing the data corresponding to the request into the memory.
Illustratively, the server 200 reads data corresponding to the request m from a hard disk or a database or other storage media, and stores the read data in its own memory.
By applying the embodiment shown in fig. 4 of the present invention, the first number corresponding to the first type of request and the second number corresponding to the second type of request are determined according to the set hit rate, each thread sends various requests to the server according to the set number, and the first type of request can continuously hit the cache of the server along with the continuous sending of the requests, so as to achieve the set hit rate.
The embodiment of the invention also provides a third pressure testing method. Fig. 5 is a schematic flow chart of a third pressure testing method according to an embodiment of the present invention, and as shown in fig. 5, based on the embodiment shown in fig. 4, in the embodiment shown in fig. 5, after step S403, step S404 is added: calculating the hit rate of all received first-class requests according to the number of the received first-class requests and the number of the received all requests, wherein the first-class requests are sent by all threads, and all the requests comprise: the first type of request and the second type of request are sent by each thread.
Illustratively, the server 200 calculates the actual request hit rate according to the quotient of the number of received requests sent by the sender 100 through all threads and the number of requests hitting the memory of the server 200 among all the requests.
By applying the embodiment shown in fig. 5 of the present invention, the request hit rate corresponding to the request sent by the sender 100 through all threads can be obtained.
Corresponding to the embodiment of the invention shown in fig. 2, the embodiment of the invention also provides a first pressure testing device. It should be noted that the first pressure testing apparatus provided in the embodiment of the present invention is preferably applied to a transmitting end.
Fig. 6 is a schematic structural diagram of a first pressure testing apparatus provided in an embodiment of the present invention, and as shown in fig. 6, an embodiment of the present invention provides a pressure testing apparatus applied to a transmitting end, where the apparatus includes: an acquisition module 601, a first setup module 602, a generation module 603, a sending module 604, and a second setup module 605, wherein,
an obtaining module 601, configured to obtain a preset request hit rate for each concurrent thread, where the request hit rate is a ratio of a number of hit requests to a total number of requests sent by a current thread;
a first setting module 602, configured to determine, according to the request hit rate, a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread;
a generating module 603, configured to generate a first number of first class requests as a current first class request, and a second number of second class requests as a current second class request;
a sending module 604, configured to send the current first type request and the current second type request to a server;
a second setting module 605, configured to use a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, where the third number is a difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and triggers the sending module 604.
By applying the embodiment shown in fig. 6 of the present invention, the request hit rate is preset, the number of requests used for performing the pressure test is calculated according to the request hit rate, and only the first type of request hits the server in each round of requests sent, so that the hit rate is relatively accurate when the embodiment of the present invention is applied to the pressure test.
Optionally, the preset number is determined according to a preset hit request change rate, and the hit request change rate is determined according to the number of different requests and the first number in every two rounds of hit requests.
Optionally, the third number of current first-type requests includes:
the first type of request is randomly selected from a first number of current first type of requests, the difference between the first number and a preset number.
By applying the embodiment of the invention, the error in the process of requesting selection can be eliminated through random selection.
Corresponding to the embodiment of the invention shown in fig. 4, the embodiment of the invention also provides a second pressure testing device. It should be noted that the second pressure testing apparatus provided in the embodiment of the present invention is preferably applied to the transmitting end.
Fig. 7 is a schematic structural diagram of a second pressure testing apparatus according to an embodiment of the present invention, where the apparatus shown in fig. 7 includes: a receiving module 701, a determining module 702, and a storing module 703, wherein,
a receiving module 701, configured to receive a request sent by a sending end, where the request includes: the method comprises the steps that a first quantity of first-class requests and a second quantity of second-class requests are sent by a sending end, and a preset request hit rate is obtained for each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread; determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests; sending the current first type request and the current second type request to a server; taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; returning to execute the step of sending the current first type request and the current second type request to the server;
a determining module 702, configured to determine, for each request, whether data corresponding to the request exists in a memory of the memory;
a storing module 703, configured to store the data corresponding to the request in the memory if the determination result of the determining module 702 is negative.
By applying the embodiment shown in fig. 7 of the present invention, the first number corresponding to the first type of request and the second number corresponding to the second type of request are determined according to the set hit rate, each thread sends various requests to the server according to the set number, and the first type of request can continuously hit the cache of the server along with the continuous sending of the requests, so as to achieve the set hit rate.
The embodiment of the invention also provides a third pressure testing device. Fig. 8 is a schematic structural diagram of a third pressure testing apparatus provided in an embodiment of the present invention, as shown in fig. 8, in the embodiment of the present invention shown in fig. 8, a calculating module 704 is added on the basis of the embodiment shown in fig. 7, and is used to calculate hit rates of all received first type requests according to the number of all received first type requests and the number of all received requests, where the first type requests are sent by all threads, and all the requests include: the first type of request and the second type of request are sent by each thread.
By applying the embodiment shown in fig. 8 of the present invention, the request hit rate corresponding to the request sent by the sender 100 through all threads can be obtained.
Corresponding to the embodiment of the invention shown in fig. 2, the invention also provides an electronic device. It should be noted that an electronic device provided by the present invention is preferably suitable for a transmitting end.
Fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, as shown in fig. 9, the electronic device 900 includes a memory 901 and a processor 902, wherein,
a memory 901 for storing a computer program;
the processor 902, when executing the program stored in the memory, implements the following steps:
acquiring a preset request hit rate aiming at each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread;
determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread;
generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests;
sending the current first type request and the current second type request to a server;
taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and returning to the step of sending the current first type request and the current second type request to the server so as to enable the server to carry out stress test.
By applying the embodiment of the invention shown in fig. 9, the request hit rate is preset, the number of requests used for pressure test is calculated according to the request hit rate, and only the first type of request hits the server in each round of requests sent, so that the hit rate is more accurate when the embodiment of the invention is applied to pressure test.
In correspondence with the embodiment of the present invention shown in fig. 2, the embodiment of the present invention further provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium runs on a computer, the computer is enabled to execute the pressure testing method of the embodiment shown in fig. 2 of the present invention.
In correspondence with the embodiment of the invention shown in fig. 2, an embodiment of the invention further provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the pressure testing method of the embodiment of the invention shown in fig. 2.
Corresponding to the embodiment of the invention shown in fig. 4, the embodiment of the invention also provides another electronic device. It should be noted that another electronic device provided by the present invention is preferably applied to a server.
Fig. 10 is a schematic structural diagram of another electronic device according to an embodiment of the present invention, as shown in fig. 10, an electronic device 1000 includes a memory 1001 and a processor 1002, wherein,
a memory 1001 for storing a computer program;
the processor 1002 is configured to implement the following steps when executing the program stored in the memory:
receiving a request sent by a sender, wherein the request comprises: the method comprises the steps that a first quantity of first-class requests and a second quantity of second-class requests are sent by a sending end, and a preset request hit rate is obtained for each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread; determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; generating a first number of first-class requests as current first-class requests and a second number of second-class requests as current second-class requests; sending the current first type request and the current second type request to a server; taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; returning to execute the step of sending the current first type request and the current second type request to the server;
judging whether data corresponding to the request exists in the memory of the mobile terminal or not aiming at each request;
and if the data corresponding to the request does not exist in the memory of the mobile terminal, storing the data corresponding to the request into the memory.
By applying the embodiment shown in fig. 10 of the present invention, the first number corresponding to the first type of request and the second number corresponding to the second type of request are determined according to the set hit rate, each thread sends various requests to the server according to the set number, and the first type of request continuously hits the cache of the server along with the continuous sending of the requests, so as to achieve the set hit rate.
In correspondence with the embodiment of the present invention shown in fig. 4, the embodiment of the present invention further provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium runs on a computer, the computer is caused to execute the pressure testing method of the embodiment shown in fig. 4 of the present invention.
In accordance with the embodiment of the present invention shown in fig. 4, the embodiment of the present invention further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the pressure testing method of the embodiment of the present invention shown in fig. 4.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the invention are brought about in whole or in part when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, the electronic device, the computer-readable storage medium, and the computer program product embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiments.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (14)
1. A pressure testing method is applied to a sending end, and the method comprises the following steps:
acquiring a preset request hit rate aiming at each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread; the hit request is a request that the data corresponding to the request is stored in the memory of the server;
determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; the first type of request is a request which can hit the memory of the server, and the second type of request is a request which can not hit the memory of the server;
generating the first quantity of first-class requests as current first-class requests and the second quantity of second-class requests as current second-class requests;
sending the current first type request and the current second type request to a server;
taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and returning to the step of sending the current first type request and the current second type request to the server so as to enable the server to perform stress test.
2. The method of claim 1, wherein the predetermined number is determined according to a predetermined hit request change rate, and wherein the hit request change rate is determined according to the first number and a number of different requests in each two hits of requests.
3. The method of claim 1, wherein the third number of current first type requests comprises:
randomly selecting from a first number of current first type requests, the first number being different from the preset number by the first type requests.
4. A pressure testing method is applied to a server, and comprises the following steps:
receiving a request sent by a sender, wherein the request comprises: the method comprises the steps that a first quantity of first-type requests and a second quantity of second-type requests are sent by a sending end, and a preset request hit rate is obtained for each concurrent thread, wherein the request hit rate is the ratio of the quantity of hit requests to the total quantity of requests sent by a current thread; determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; generating the first quantity of first-class requests as current first-class requests and the second quantity of second-class requests as current second-class requests; sending the current first type request and the current second type request to a server; taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; returning to execute the step of sending the current first type request and the current second type request to the server; the hit request is a request that the data corresponding to the request is stored in the memory of the server; the first type of request is a request which can hit the memory of the server, and the second type of request is a request which can not hit the memory of the server;
judging whether data corresponding to the request exists in a memory of the mobile terminal or not aiming at each request;
and if the data corresponding to the request does not exist in the memory of the mobile terminal, storing the data corresponding to the request into the memory.
5. The method of claim 4, wherein after storing the data corresponding to the request in memory, the method further comprises:
calculating the hit rate of all received first-class requests according to the number of the received first-class requests and the number of the received all requests, wherein the first-class requests are sent by all threads, and the all requests comprise: the first type of request and the second type of request are sent by each thread.
6. A pressure test device is applied to a sending end, and comprises: an acquisition module, a first setting module, a generation module, a sending module, and a second setting module, wherein,
the obtaining module is used for obtaining a preset request hit rate aiming at each concurrent thread, wherein the request hit rate is the ratio of the number of hit requests to the total number of requests sent by the current thread; the hit request is a request that the data corresponding to the request is stored in the memory of the server;
the first setting module is used for determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; the first type of request is a request which can hit the memory of the server, and the second type of request is a request which can not hit the memory of the server;
the generation module is configured to generate the first number of first-class requests as a current first-class request and the second number of second-class requests as a current second-class request;
the sending module is used for sending the current first type request and the current second type request to a server;
the second setting module is configured to use a preset number of current second type requests and a third number of current first type requests as current first type requests, where the third number is a difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; and returning to the step of sending the current first type request and the current second type request to the server so as to enable the server to perform stress test.
7. The apparatus of claim 6, wherein the predetermined number is determined according to a predetermined hit request change rate, and wherein the hit request change rate is determined according to the first number and a number of different requests in each round of hit requests.
8. The apparatus of claim 6, wherein the third number of current first type requests comprises:
randomly selecting from a first number of current first type requests, the first number being different from the preset number by the first type requests.
9. A pressure testing device is applied to a server, and the device comprises: a receiving module, a judging module and a storage module, wherein,
the receiving module is configured to receive a request sent by a sending end, where the request includes: the method comprises the steps that a first quantity of first-type requests and a second quantity of second-type requests are sent by a sending end, and a preset request hit rate is obtained for each concurrent thread, wherein the request hit rate is the ratio of the quantity of hit requests to the total quantity of requests sent by a current thread; determining a first quantity corresponding to the first type of request and a second quantity corresponding to the second type of request according to the request hit rate; taking the first quantity as the quantity of the requests hit by the current thread; taking the sum of the first quantity and the second quantity as the total quantity of the requests sent by the current thread; generating the first quantity of first-class requests as current first-class requests and the second quantity of second-class requests as current second-class requests; sending the current first type request and the current second type request to a server; taking a preset number of current second-class requests and a third number of current first-class requests as current first-class requests, wherein the third number is the difference between the first number and the preset number; taking a second number of second-class requests which are regenerated and different from the generated requests as current second-class requests; returning to execute the step of sending the current first type request and the current second type request to the server; the hit request is a request that the data corresponding to the request is stored in the memory of the server; the first type of request is a request which can hit the memory of the server, and the second type of request is a request which can not hit the memory of the server;
the judging module is used for judging whether data corresponding to the request exists in the memory of the judging module aiming at each request;
and the storage module is used for storing the data corresponding to the request into a memory under the condition that the judgment result of the judgment module is negative.
10. The apparatus of claim 9, further comprising a calculating module, configured to calculate a hit rate of all first type requests received according to a number of all first type requests received and a number of all requests received, wherein the first type requests are sent by all threads, and the all requests include: the first type of request and the second type of request are sent by each thread.
11. An electronic device comprising a memory and a processor;
the memory is used for storing a computer program;
the processor, when executing the program stored in the memory, implementing the method steps of any of claims 1-3.
12. An electronic device comprising a memory and a processor;
the memory is used for storing a computer program;
the processor, when executing the program stored in the memory, implementing the method steps of any of claims 4-5.
13. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of the claims 1-3.
14. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any of the claims 4-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810091852.4A CN108574610B (en) | 2018-01-30 | 2018-01-30 | Pressure testing method and device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810091852.4A CN108574610B (en) | 2018-01-30 | 2018-01-30 | Pressure testing method and device, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108574610A CN108574610A (en) | 2018-09-25 |
| CN108574610B true CN108574610B (en) | 2020-10-20 |
Family
ID=63576668
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810091852.4A Active CN108574610B (en) | 2018-01-30 | 2018-01-30 | Pressure testing method and device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108574610B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109491895A (en) * | 2018-10-26 | 2019-03-19 | 北京车和家信息技术有限公司 | Server stress test method and device |
| CN109542712B (en) * | 2018-11-02 | 2023-04-07 | 平安科技（深圳）有限公司 | Server pressure testing method and device, computer equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101217425A (en) * | 2008-01-04 | 2008-07-09 | 中兴通讯股份有限公司 | Web testing method and device |
| CN102955721A (en) * | 2011-08-16 | 2013-03-06 | 阿里巴巴集团控股有限公司 | Device and method for pressure generation for testing |
| CN107220165A (en) * | 2016-03-21 | 2017-09-29 | 阿里巴巴集团控股有限公司 | The method and apparatus of pressure test on a kind of artificial line |
-
2018
- 2018-01-30 CN CN201810091852.4A patent/CN108574610B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101217425A (en) * | 2008-01-04 | 2008-07-09 | 中兴通讯股份有限公司 | Web testing method and device |
| CN102955721A (en) * | 2011-08-16 | 2013-03-06 | 阿里巴巴集团控股有限公司 | Device and method for pressure generation for testing |
| CN107220165A (en) * | 2016-03-21 | 2017-09-29 | 阿里巴巴集团控股有限公司 | The method and apparatus of pressure test on a kind of artificial line |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108574610A (en) | 2018-09-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20150095892A1 (en) | Systems and methods for evaluating a change pertaining to a service or machine | |
| CN107342913B (en) | Detection method and device for CDN node | |
| JP6721057B2 (en) | Communication session log analysis device and method | |
| CN108574610B (en) | Pressure testing method and device, electronic equipment and medium | |
| KR20160056944A (en) | Acceleration based on cached flows | |
| CN111562884B (en) | Data storage method and device and electronic equipment | |
| CN104144223B (en) | A kind of data capture method and device | |
| CN111030888A (en) | Domain name system DNS capacity measuring method, device, equipment and medium | |
| CN111443899B (en) | Element processing method and device, electronic equipment and storage medium | |
| US20190012348A1 (en) | Data aggregation method and device | |
| CN109726340A (en) | The querying method and device of uniform resource locator classification | |
| CN110430070B (en) | Service state analysis method, device, server, data analysis equipment and medium | |
| CN112134958B (en) | Data request method, device, server and storage medium | |
| US20150286753A1 (en) | Estimating Think Times | |
| CN108089972A (en) | interface test method and device | |
| US10742758B2 (en) | Communication analysis device, communication analysis method, and program recording medium | |
| CN110677683B (en) | Video storage and video access method and distributed storage and video access system | |
| CN107018039B (en) | Method and device for testing performance bottleneck of server cluster | |
| CN110020166B (en) | Data analysis method and related equipment | |
| CN113014443B (en) | Method and system for testing whether CDN (content delivery network) resources hit cache | |
| CN114780388A (en) | Concurrency test method and device based on domestic operating system software store | |
| US11243857B2 (en) | Executing test scripts with respect to a server stack | |
| CN112910936B (en) | Data processing method, device and system, electronic equipment and readable storage medium | |
| CN112882646A (en) | Resource caching method and device, electronic equipment and storage medium | |
| WO2022222665A1 (en) | Request recognition method and apparatus, and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |