CN112363879B - Cache server performance test method, device, equipment and medium - Google Patents

Abstract

The embodiments of the present disclosure disclose a cache server performance test method, apparatus, device and medium. A specific implementation of the method includes: sending a request to a target server to obtain a cache server performance test task; performing a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server, and obtaining the test result of the performance test operation; sending the test result to the target server. This implementation can more accurately reflect the network and service conditions of the real users of the client. Furthermore, after scheduling the cache server according to the cache server performance test results, the service request time can be reduced to a certain extent.

Description

Cache server performance testing method, device, equipment and medium

Technical Field

Embodiments of the present disclosure relate to the field of computer technology, and in particular to a cache server performance testing method, apparatus, device, and medium for a client.

Background Art

Cache server performance testing refers to a method of determining the performance of a cache server through certain technical means. At present, when performing performance testing on a cache server, the method usually adopted is: testing the performance of the cache server through a third-party cache server performance testing platform.

However, when using the above method to test cache server performance, the following technical problems often occur:

Existing methods rarely test the performance of cache servers from the client's perspective, making it difficult for cache server performance test results to accurately reflect the network and service conditions of the client's real users, which in turn makes it difficult to reduce the time of service requests after scheduling the cache server according to the cache server performance test results.

Summary of the invention

The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

Some embodiments of the present disclosure propose a cache server performance testing method, apparatus, device and medium for a client to solve one or more of the technical problems mentioned in the above background technology section.

In a first aspect, some embodiments of the present disclosure provide a cache server performance testing method for a client, the method comprising: sending a request to a target server to obtain a cache server performance testing task; performing a performance testing operation on the target cache server based on task information of the cache server performance testing task returned by the target server, and obtaining a test result of the performance testing operation; and sending the test result to the target server.

In a second aspect, some embodiments of the present disclosure provide a device for cache server performance testing of a client, the device comprising: a first sending unit, configured to send a request for obtaining a cache server performance testing task to a target server; an execution unit, configured to perform a performance testing operation on the target cache server according to task information of the cache server performance testing task returned by the target server, and obtain a test result of the performance testing operation; and a second sending unit, configured to send the test result to the target server.

In a third aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation manner of the above-mentioned first aspect.

In a fourth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any implementation manner of the above-mentioned first aspect is implemented.

The above-mentioned various embodiments of the present disclosure have the following beneficial effects: through the cache server performance testing method for the client of some embodiments of the present disclosure, the network and service conditions of the real users of the client can be reflected more accurately. Specifically, the reason why the relevant cache server performance testing method is difficult to more accurately reflect the network and service conditions of the real users of the client is that the existing methods rarely test the performance of the cache server from the perspective of the client. Based on this, the cache server performance testing method for the client of some embodiments of the present disclosure starts from the perspective of the client, and the client actively obtains the cache server performance test task and performs the corresponding test operation. It does not rely on a third-party test platform, and the test process completely relies on the client itself, so that the test results can reflect the real test data of the client. Therefore, it can more accurately reflect the network and service conditions of the real users of the client. Furthermore, after scheduling the cache server according to the cache server performance test results, the service request time can be reduced to a certain extent.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

FIG1 is a schematic diagram of an application scenario of a cache server performance testing method for a client according to some embodiments of the present disclosure;

FIG2 is a flow chart of some embodiments of a cache server performance testing method for a client according to the present disclosure;

FIG3 is a flow chart of other embodiments of a cache server performance testing method for a client according to the present disclosure;

FIG4 is a schematic diagram of the structure of some embodiments of a cache server performance testing device for a client according to the present disclosure;

FIG. 5 is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

FIG. 1 is a schematic diagram of an application scenario of a cache server performance testing method for a client according to some embodiments of the present disclosure.

In the application scenario of FIG1 , first, the computing device 101 may send a request 103 for obtaining a cache server performance test task to the target server 102. Next, the computing device 101 may perform a performance test operation 105 on the target cache server according to the task information 104 of the cache server performance test task returned by the target server 102, and obtain a test result 106 of the performance test operation 105. Finally, the computing device 101 may send the test result 106 to the target server 102.

It should be noted that the computing device 101 can be hardware or software. When the computing device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or it can be implemented as a single server or a single terminal device. When the computing device is embodied as software, it can be installed in the hardware devices listed above. It can be implemented as multiple software and software modules for providing distributed services, for example, or it can be implemented as a single software or software module. No specific limitation is made here.

It should be understood that the number of computing devices in FIG1 is merely illustrative and any number of computing devices may be provided according to implementation requirements.

2, a process 200 of some embodiments of the cache server performance testing method for a client according to the present disclosure is shown. The cache server performance testing method for a client includes the following steps:

Step 201: Send a request for obtaining a cache server performance test task to a target server.

In some embodiments, the execution subject of the cache server performance test method for the client (the computing device 101 as shown in FIG. 1 ) can send a request for obtaining a cache server performance test task to the target server through a wired connection or a wireless connection. Among them, the above-mentioned target server can be a server that provides the above-mentioned client with a method that can be called by the client application. The request for the above-mentioned cache server performance test task may include: the target server IP address (Internet Protocol Address), the client unique identification code. The above-mentioned target server IP address can be used to indicate the location of the above-mentioned target server. The above-mentioned execution subject can send the above-mentioned request for obtaining the cache server performance test task to the above-mentioned target server according to the above-mentioned target server IP address. The above-mentioned client unique identification code can be used to uniquely identify the above-mentioned client. The above-mentioned target server can determine whether it is necessary to send the task information of the cache server performance test task to the corresponding client according to the above-mentioned client unique identification code. It can be understood that in this way, the above-mentioned target server needs to predetermine the client unique identification code of the client that needs to receive the task information of the cache server performance test task.

In some optional implementations of some embodiments, the execution subject may send a request to the target server to obtain a cache server performance test task in response to determining that the number of client startups within a preset time period meets the first preset condition. The end time point of the preset time period may be the current time point. The end time point of the preset time period may also be 23:59:59 on the same day. The first preset condition may be that the number of client startups is less than or equal to the preset number of startups. The request to obtain the cache server performance test task may include: the target server host name, the client login user unique identification code. The target server host name may be used to uniquely identify a server. The client login user unique identification code may be used to uniquely identify the user who logs in to the client. The target server may determine whether it is necessary to send the task information of the cache server performance test task to the corresponding client based on the client login user unique identification code. It can be understood that in this way, the target server needs to predetermine the client login user unique identification code of the client that needs to receive the task information.

In the above implementation, the timing of sending a request to the target server to obtain the cache server performance test task is increased, which is more compatible with the actual application scenario and more applicable. It can avoid the consumption of memory resources and network resources of the terminal device where the client is located by frequently sending requests to the target server.

As an example, the preset time period may be 24 hours. The end time point of the preset time period may be 23:59:59 on the same day. The preset number of starts may be 2 times.

Step 202: Perform a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server, and obtain a test result of the performance test operation.

In some embodiments, the task information may include: a set of test websites for cache server performance testing. The execution subject performs a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server to obtain the test result of the performance test operation, which may include the following steps:

The first step is to send a resource acquisition request to the target cache server according to each test URL in the test URL set.

The second step is to obtain the cache server response time associated with the resource acquisition request corresponding to each test URL in the test URL set, and obtain a cache server response time set. The cache server response time may refer to the time interval between the time when the target cache server sends the resource acquisition request and the time when the target cache server receives the resource returned.

The third step is to determine the average value of the response time of each cache server in the above cache server response time set to obtain the average response time of the cache servers, and use the above average response time of the cache servers as the test result of the performance test operation.

In some optional implementations of some embodiments, the task information may include: a test website for cache server performance testing. The execution subject performs a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server, which may include the following steps:

The first step is to send a resource acquisition request to the target cache server according to the test URL.

The second step is to obtain response information related to the resource acquisition request, and use the response information as the test result of the performance test operation, wherein the response information may include at least one of the following: domain name resolution time, transmission control protocol TCP connection time, secure socket protocol SSL handshake time, cache server response time, resource transmission speed, and request result information. The request result information may be information indicating whether the resource is successfully acquired.

In some optional implementations of some embodiments, the execution subject may, in response to determining that the client startup time satisfies a second preset condition, perform the cache server performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server. The second preset condition may be that the client startup time is less than the preset startup time.

In the above implementation, a description of the timing of the target cache server performing the performance test operation of the cache server is added. The client startup time can reflect the jamming degree of the terminal device where the client is located to a certain extent. The shorter the startup time, the lower the jamming degree of the terminal device. Through the second preset condition, the performance test operation of the cache server can be performed when the jamming degree of the terminal device is low, reducing the impact of the terminal device's own state on the test operation results. It has a higher degree of matching with actual application scenarios and is more applicable.

In some optional implementations of some embodiments, the target cache server may be determined by the following steps: determining the cache server indicated by the domain name resolution result of the test website as the target cache server, wherein the domain name resolution result may be an IP address.

Step 203: Send the test result to the target server.

In some embodiments, the execution entity may send the test result of the performance test operation to the target server via a wired connection or a wireless connection.

The above-mentioned various embodiments of the present disclosure have the following beneficial effects: through the cache server performance testing method for the client of some embodiments of the present disclosure, the network and service conditions of the real users of the client can be reflected more accurately. Specifically, the reason why the relevant cache server performance testing method is difficult to more accurately reflect the network and service conditions of the real users of the client is that the existing methods rarely test the performance of the cache server from the perspective of the client. Based on this, the cache server performance testing method for the client of some embodiments of the present disclosure starts from the perspective of the client, and the client actively obtains the cache server performance test task and performs the corresponding test operation. It does not rely on a third-party test platform, and the test process completely relies on the client itself, so that the test results can reflect the real test data of the client. Therefore, it can more accurately reflect the network and service conditions of the real users of the client. Furthermore, after scheduling the cache server according to the cache server performance test results, the service request time can be reduced to a certain extent.

Further referring to Fig. 3, it shows a process 300 of another embodiment of a cache server performance testing method for a client. The process 300 of the cache server performance testing method for a client comprises the following steps:

Step 301: Send a request to a target server to obtain a cache server performance test task.

Step 302: Perform a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server to obtain a test result of the performance test operation.

Step 303: Send the test result to the target server.

In some embodiments, the specific implementation of steps 301-303 and the technical effects brought about by them can refer to steps 201-203 in the embodiment corresponding to Figure 2, and will not be repeated here.

Step 304: determine the device status information of the terminal device where the client is located.

In some embodiments, the execution entity may determine the device status information of the terminal device where the client is located. The device status information may include but is not limited to at least one of the following: load information, communication signal strength information, and network information. The load information may be the CPU (Central Processing Unit) load of the terminal device. The communication signal strength information may refer to the frequency at which the terminal device receives the communication signal. The network information may refer to the network type of the network to which the terminal device is connected, for example, a 4G network, a 5G network, and the like.

Step 305: Send the device status information to the target server.

In some embodiments, the execution entity may send the device status information to the target server via a wired connection or a wireless connection.

As can be seen from FIG. 3, compared with the description of some embodiments corresponding to FIG. 2, the process 300 of the cache server performance test method for the client in some embodiments corresponding to FIG. 3 embodies the steps of determining device status information and sending the device status information to the target server. Thus, when the target server evaluates the target cache server according to the test results, it can take into account the impact of the device status on the above test results, thereby more realistically evaluating the performance of the target cache server. Furthermore, the cache server can be reasonably scheduled to reduce the time of service requests.

Further referring to FIG. 4 , as an implementation of the above methods in the above figures, the present disclosure provides some embodiments of a cache server performance testing device for a client, and these device embodiments correspond to the method embodiments described above in FIG. 2 , and the device can be specifically applied in various electronic devices.

As shown in FIG4 , a cache server performance test device 400 for a client in some embodiments includes: a first sending unit 401, an execution unit 402, and a second sending unit 403. The first sending unit 401 is configured to send a request for obtaining a cache server performance test task to a target server. The execution unit 402 is configured to perform a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server, and obtain a test result of the performance test operation. The second sending unit 403 is configured to send the test result to the target server.

In an optional implementation of some embodiments, the cache server performance test device 400 for a client may further include: a determination unit and a third sending unit. The determination unit may be configured to determine device status information of a terminal device where the client is located, wherein the device status information includes at least one of the following: load information, communication signal strength information, and network information. The third sending unit may be configured to send the device status information to the target server.

In an optional implementation of some embodiments, the first sending unit 401 may also be configured to: in response to determining that the number of client startups within a preset time period satisfies a first preset condition, send a request to the target server to obtain a cache server performance test task.

In an optional implementation of some embodiments, the above-mentioned task information includes: a test website address used for cache server performance testing.

In an optional implementation of some embodiments, the execution unit 402 may also be configured to: send a resource acquisition request to the target cache server according to the test URL; obtain response information related to the resource acquisition request, wherein the response information includes at least one of the following: domain name resolution time, transmission control protocol TCP connection time, secure socket protocol SSL handshake time, cache server response time, resource transmission speed, and request result information.

In an optional implementation of some embodiments, the execution unit 402 may be further configured to: in response to determining that the client startup time satisfies a second preset condition, perform the performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server.

In an optional implementation manner of some embodiments, the target cache server may be determined by the following steps: determining the cache server indicated by the domain name resolution result of the test URL as the target cache server.

It is understandable that the units recorded in the device 400 correspond to the steps in the method described with reference to Figure 2. Therefore, the operations, features and beneficial effects described above for the method are also applicable to the device 400 and the units contained therein, and will not be repeated here.

Referring to FIG5, a schematic diagram of an electronic device (such as the computing device 101 in FIG1) 500 suitable for implementing some embodiments of the present disclosure is shown. The electronic device shown in FIG5 is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

As shown in FIG5 , the electronic device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to the bus 504.

Typically, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 508 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Although FIG. 5 shows an electronic device 500 with various devices, it should be understood that it is not required to implement or have all the devices shown. More or fewer devices may be implemented or have alternatively. Each box shown in FIG. 5 may represent one device, or may represent multiple devices as needed.

In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.

It should be noted that the computer-readable medium in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

The computer-readable medium may be included in the device; or it may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: sends a request to obtain a cache server performance test task to the target server; performs a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server, and obtains the test result of the performance test operation; and sends the test result to the target server.

Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and/or flow chart, and the combination of the square boxes in the block diagram and/or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

The units described in some embodiments of the present disclosure may be implemented by software or by hardware. The units described may also be provided in a processor, for example, may be described as: a processor includes a first sending unit, an execution unit, and a second sending unit. The names of these units do not, in some cases, constitute limitations on the units themselves, for example, the first sending unit may also be described as "a unit that sends a request to a target server to obtain a cache server performance test task".

The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) and the technical solutions formed.

Claims (8)

1. A cache server performance testing method for a client, comprising: In response to determining that the number of client startups within a preset time period meets a first preset condition, sending a request to the target server to obtain a cache server performance test task, wherein the first preset condition is that the number of client startups is less than or equal to a preset number of startups; In response to determining that the client startup time satisfies a second preset condition, a performance test operation is performed on the target cache server according to a set of test URLs for cache server performance testing included in the task information of the cache server performance test task returned by the target server, to obtain a test result of the performance test operation, wherein the second preset condition is that the client startup time is less than a preset startup time, including: sending a resource acquisition request to the target cache server according to each test URL in the test URL set; obtaining a cache server response time associated with the resource acquisition request corresponding to each test URL in the test URL set, to obtain a cache server response time set; determining an average value of the response time of each cache server in the cache server response time set, to obtain an average cache server response time, and using the average cache server response time as the test result of the performance test operation; The test result is sent to the target server. 2. The method according to claim 1, wherein the method further comprises: Determine device status information of the terminal device where the client is located, wherein the device status information includes at least one of the following: load information, communication signal strength information, and network information; The device status information is sent to the target server. 3. The method according to claim 1, wherein the task information includes: a test website address for cache server performance testing. 4. The method according to claim 3, wherein the step of performing a performance test operation on the target cache server according to the task information of the cache server performance test task returned by the target server comprises: According to the test URL, sending a resource acquisition request to the target cache server; Obtain response information related to the resource acquisition request, and use the response information as the test result of the performance test operation, wherein the response information includes at least one of the following: domain name resolution time, transmission control protocol TCP connection time, secure socket protocol SSL handshake time, cache server response time, resource transmission speed, and request result information. 5. The method according to claim 1, wherein the target cache server is determined by the following steps: The cache server indicated by the domain name resolution result of the test website is determined as the target cache server. 6. A cache server performance testing device for a client, comprising: A first sending unit is configured to send a request for obtaining a cache server performance test task to a target server in response to determining that the number of client startups within a preset time period meets a first preset condition, wherein the first preset condition is that the number of client startups is less than or equal to a preset number of startups; The execution unit is configured to, in response to determining that the client startup time meets a second preset condition, perform a performance test operation on the target cache server according to a test URL set for cache server performance testing included in the task information of the cache server performance test task returned by the target server, and obtain a test result of the performance test operation, wherein the second preset condition is that the client startup time is less than a preset startup time, including: sending a resource acquisition request to the target cache server according to each test URL in the test URL set; obtaining a cache server response time related to the resource acquisition request corresponding to each test URL in the test URL set, and obtaining a cache server response time set; determining an average value of the response time of each cache server in the cache server response time set, and obtaining a cache server average response time, and using the cache server average response time as the test result of the performance test operation; The second sending unit is configured to send the test result to the target server. 7. An electronic device comprising: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 5. 8. A computer readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.