WO2015090248A1

WO2015090248A1 - Server overload protection method and device

Info

Publication number: WO2015090248A1
Application number: PCT/CN2015/073012
Authority: WO
Inventors: 苏士杰
Original assignee: 腾讯科技（深圳）有限公司
Priority date: 2013-12-16
Filing date: 2015-02-13
Publication date: 2015-06-25
Also published as: CN104142862B; CN104142862A

Abstract

Disclosed are a server overload protection method and device. The method comprises: a request to be processed is received, and current system load information of a server is obtained (101); the current system load information of the server is compared with a preset system load threshold, and according to a comparison result, it is determined whether the server is overloaded (102); if it is determined that the server is overloaded, processing of the request to be processed is refused (103). The device comprises: a first receiving module (401), a first obtaining module (402), a first determining module (403) and a processing module (404). Since the system load information of the server is certain, the true situation of whether the server is overloaded can be reflected. Therefore, by comparing the obtained current system load information of the server with the preset system load threshold, and refusing to process the request to be processed when it is determined according to the comparison result that the server is overloaded, the present invention can accurately determine whether the server is overloaded, thereby performing better overload protection on the server.

Description

Server overload protection method and device

Technical field

The present invention relates to the field of Internet technologies, and in particular, to a server overload protection method and apparatus.

Background technique

With the rapid development of Internet technology, more and more user access requests need to be processed by servers. However, due to the limitations of the server's own processing capabilities, the number of user access requests that any one server can process in a given period of time is limited. When the number of users connected to the server exceeds a certain number, if the server does not have enough capacity to handle the user access request that comes with it, the server will be overloaded and may cause adverse consequences such as downtime, resulting in huge economic losses. Therefore, in order to prevent the above situation, it is usually necessary to adopt a certain method to protect the server that may generate an overload.

Summary of the invention

The embodiment of the invention provides a method and device for overload protection of a server. The technical solution is as follows:

In one aspect, a method for overload protection of a server is provided, the method comprising:

Receiving a pending request and obtaining current system load information of the server;

Comparing the current system load information of the server with a preset system load threshold, and determining whether the server is overloaded according to the comparison result;

If it is determined that the server is overloaded, the processing of the pending request is refused.

In another aspect, an overload protection device for a web server is provided, the device including a processor And a processor readable storage medium having a plurality of modules stored on the processor readable storage medium, including:

a first receiving module, configured to receive a pending request;

a first acquiring module, configured to acquire current system load information of the server;

a first determining module, configured to compare the current system load information of the server with a preset system load threshold, and determine whether the server is overloaded according to the comparison result;

And a processing module, configured to refuse to process the to-be-processed request when determining that the server is overloaded.

The beneficial effects brought by the technical solutions provided by the embodiments of the present invention are:

Since the system load information of the server is deterministic, the system load threshold can reflect the real situation of whether the server is overloaded. Therefore, by comparing the current system load information of the server with a preset system load threshold, the comparison result can be Accurately determine whether the server is overloaded, so as to ensure better overload protection of the server by refusing to process the request when determining that the server is overloaded.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a flowchart of a method for overload protection of a server according to Embodiment 1 of the present invention;

2 is a flowchart of a method for overload protection of a server according to Embodiment 2 of the present invention;

3 is a flowchart of a method for overload protection of a server according to Embodiment 3 of the present invention;

4 is a schematic structural diagram of an overload protection device for a server according to Embodiment 4 of the present invention;

FIG. 5 is a schematic structural diagram of an overload protection device for a server according to Embodiment 5 of the present invention.

detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

Embodiment 1

Due to the limitation of the processing power of the server itself, the number of requests that any one server can process in a certain period of time is limited. When the server receives more than a certain number of pending requests, the server will be overloaded and may cause downtime. Such adverse consequences, resulting in huge economic losses. Therefore, in order to prevent the above situation, the embodiment of the present invention provides a method for overload protection of a server. In this embodiment, the method provided in this embodiment is described by using the system load information of the server as a basis for determining whether the server is overloaded. Referring to FIG. 1, the method process provided by this embodiment includes:

101: Receive a pending request, and obtain current system load information of the server;

The current system load information of the server is obtained, including but not limited to:

When the system load information of the pre-stored server expires, the system load information of the server is re-acquired, and the obtained system load information is used as the current system load information of the server.

Optionally, obtaining current system load information of the server, including but not limited to:

When the system load information of the pre-stored server has not expired, the system load information of the pre-stored server is read, and the read system load information is used as the current system load information of the server.

Further, before acquiring the current system load information of the server, the method further includes:

Pre-fetch and store the system load information of the server.

102: Compare the current system load information of the server with a preset system load threshold. Right, and based on the comparison results to determine whether the server is overloaded;

Before comparing the current system load information of the server with the preset system load threshold, it also includes:

Receive system load threshold setting commands and set and store system load thresholds based on system load threshold setting commands.

Optionally, after receiving the system load threshold setting command, the method further includes:

Determine whether the system load threshold setting command is legal;

If it is determined that the system load threshold setting command is legal, the step of setting and storing the system load threshold according to the system load threshold setting command is performed.

103: If it is determined that the server is overloaded, the processing request is rejected.

Optionally, before refusing to process the processing request, it also includes:

Obtaining the number of times the request is rejected during the preset time period, and determining whether to reject the pending request according to the obtained number of times of rejecting the processing request;

If it is determined that the pending request is refused to be processed, the step of rejecting the processing of the processing request is performed.

Obtain a random number and determine whether the random number is the same as the preset value;

Determining whether to refuse to process the pending request according to the judgment result;

In the method provided in this embodiment, since the system load information of the server is deterministic, the system load threshold can reflect the real situation of whether the server is overloaded. Therefore, the current system load information of the server is compared with a preset system load threshold. After that, according to the comparison result, it is possible to accurately determine whether the server is overloaded, thereby achieving better overload protection of the server by rejecting the processing of the processing request when determining that the server is overloaded.

Embodiment 2

An embodiment of the present invention provides a method for protecting an overload of a server. The method provided in this embodiment is described by taking the example of the server as an example. Referring to FIG. 2, the method process provided by this embodiment includes:

201: Receive a pending request, and obtain current system load information of the server.

Specifically, the embodiment does not specifically limit the type of the to-be-processed request, including but not limited to a connection request, a service request, and the like. This embodiment does not specifically limit the content of the current system load information of the server, including but not limited to the current local resource usage rate of the server. The local resource usage rate includes at least one of a CPU (Central Processing Unit) usage rate, a memory usage rate, and a network bandwidth usage rate. The manner of obtaining the current system load information of the server is also not limited in this embodiment, including but not limited to the following two methods:

The first way: directly obtain the current system load information of the server;

For the first mode, the system load information of the server is used as the local resource usage rate of the server. This embodiment does not specifically limit the manner in which the current system load information of the server is directly obtained, including but not limited to the server local according to the measurement. The specific usage of the resource, calculate the usage rate of each resource, and use the calculated usage rate of each resource as the current system load information of the obtained server.

For example, if the local resource to be used is memory, the memory on the server is 8 GB. At a certain point in time, the network application on the server occupies 4 GB of memory, and the memory usage on the current server is 50. %, the calculated memory usage is 50% as a system load information obtained.

The second way: pre-acquisition and storage of the server's system load information, according to pre-stored The system load information of the server obtains the current system load information of the server. The method for pre-acquiring the system load information of the server may be performed according to the foregoing first manner. After acquiring the system load information of the server, the system load information may be stored in a storage medium on the server. Then, according to whether the system load information of the pre-stored server expires to determine how to obtain the current system load information of the server, the following can be divided into the following two cases:

In the first case, when the system load information of the pre-stored server expires, the system load information of the server is re-acquired, and the obtained system load information is used as the current system load information of the server;

Wherein, determining whether the system load information of the pre-stored server is expired may be as follows:

Set a time period. When the system load information of the server is pre-stored, the specific time for storing the system load information can be recorded at the same time. When a new pending request arrives, obtain the specific time at this time, and subtract the specific time of the storage system load information from the specific time obtained. If the obtained difference is smaller than the previously set time period, determine The system load information of the pre-stored server has not expired. Otherwise, it is determined that the system load information of the pre-stored server has expired. Certainly, the system load information of the pre-stored server may be determined to be expired, which is not specifically limited in this embodiment. In addition, the value of the time period can be set as needed, and this embodiment is also not specifically limited. In order to make the stored system load information reflect the real situation of the current system load information of the server, the set time period is as small as possible.

For example, taking the memory usage rate as the system load information as an example, the memory usage rate obtained by the server is 60% at 10:30, and the preset time period is 5 minutes. If a new one arrives at 10:34, For the pending request, the difference between 10:34 and 10:30 is 4 minutes, which is less than the preset time period of 5 minutes. Therefore, it can be judged that the system load information of the pre-stored server has not expired. If a new pending request comes at 10:36, 10:36 and 10 The difference of 30 points is 6 minutes, which is greater than the preset time period of 5 minutes. Therefore, it can be judged that the system load information of the pre-stored server has expired.

When the system load information of the pre-stored server expires, the system load information of the server may be re-acquired according to the first manner, and the obtained system load information is used as the current system load information of the server. Further, after the system load information is obtained, the acquired system load information may be updated to the storage medium of the server, and the specific time for storing the system load information is updated at the same time, which is not specifically limited in this embodiment.

In the second case, when the system load information of the pre-stored server is not expired, the system load information of the pre-stored server is read, and the read system load information is used as the current system load information of the server.

For the second case, since the system load information of the server has stability within a certain period of time, for example, the CPU usage of a system load information measured to the server is 60% at 10:35:30, after this time. Within 3 seconds, the CPU usage of the server measured at 10:35:31 may be 60.1%, that is, the CPU usage varies little and has stability within 3 seconds. After the server obtains the current system load information, the system load information acquired before is still referenced within a certain period of time. Therefore, it can be determined whether the system load information of the pre-stored server is expired, when the pre-stored server is When the system load information expires, it can be stated that the previously obtained system load information is not referenced. When the system load information of the pre-stored server has not expired, the pre-stored system load information is read, and the read system load information is used as the current system load information of the server.

It should be noted that, since it takes a certain time and resources to acquire the current system load information of the server each time, the stability of the system load information of the server is utilized in a certain period of time, according to the second method described above, the current system of the server. Load information is obtained, which can shorten the acquisition The time taken by the server for current system load information, while saving server resources, thereby improving the efficiency of obtaining the current system load information of the server.

202: Compare the current system load information of the server with a preset system load threshold;

Specifically, if the system load information of the server is the local resource usage rate of the server, the system load threshold is a local resource usage threshold.

Specifically, the specific value of the system load threshold may be set according to the specific performance of the system or the specific requirements. This embodiment does not specifically limit this, including but not limited to the following:

Receive system load threshold setting command, set and store system load threshold according to system load threshold setting command. The system load threshold setting command may adopt a URL (Uniform Resource Locator) format. After receiving the URL format command, the server parses the received URL format command, obtains the system load threshold carried in the URL format command, and obtains the system load threshold. The system load threshold is stored. The system load threshold setting command may also adopt other formats, such as a text message format, which is not specifically limited in this embodiment.

It should be noted that, if the system load information includes multiple types of information, when setting the corresponding system load threshold, it is necessary to set a corresponding system load threshold for each system load information. For example, if the system load information includes the usage rate of multiple local resources and the system load threshold is a usage threshold of multiple local resources, the local resource usage rate needs to be set for each local resource when setting the local resource usage threshold. Threshold. In addition, after the setting of the system load threshold is performed for the first time according to the system load threshold setting command, the method provided in this embodiment further supports receiving the system load threshold setting command again in subsequent operations, according to the re-received system load threshold. The setup command again sets the system load threshold to update the system load threshold. The number of times the system load threshold setting command is received is not specifically limited in this embodiment.

Further, no matter whether the system load threshold setting command is received, the system load threshold setting command may be determined to be legal after receiving the system load threshold setting command. When the system load threshold setting command is determined to be legal, the system is determined according to the system. The load threshold setting command sets and stores the system load threshold. The system load threshold setting command may be determined according to the IP (Internet Protocol) address of the device that sends the system load threshold setting command, or the system load threshold may be determined according to whether the format of the system load threshold setting command is correct. Set whether the command is legal.

If the system load threshold setting command is used to determine whether the system load threshold setting command is legal, the blacklist of the malicious IP address can be stored in the server in advance, and the system load threshold setting sent by a device is obtained. The command can determine whether the IP address of the device is in the blacklist of the malicious IP address. If the IP address of the device is in the blacklist, the system load threshold setting command sent by the device is invalid. Alternatively, the whitelist of the legal IP address may be stored on the server in advance. If the IP address of the device is not in the whitelist, the system load threshold setting command sent by the device may be determined to be invalid. Further, the server obtains a legal or malicious IP address, which can be obtained according to the historical record. This embodiment does not specifically limit the manner in which the server obtains a legal or malicious IP address, and does not determine the IP address of the device according to the system load threshold setting command. The manner in which the system load threshold setting command is legal is specifically limited.

203: Determine, according to the comparison result, whether the server is overloaded;

Specifically, the comparison result may include but is not limited to the following two types:

The first type: the current system load information of the server is greater than a preset system load threshold;

Second: The current system load information of the server is less than or equal to the preset system load threshold.

If it is determined whether the server is overloaded according to the comparison result, if the comparison result is the first type, the server overload may be determined. If the comparison result is the second type, it may be determined that the server is not overloaded.

For example, the pre-set system load threshold is 90% CPU usage and 80% memory usage. When the current system load information of the server is 92% of the CPU usage and 87% of the memory usage rate, after comparing the current system load information of the server with the preset system load threshold, the comparison result is the current server. If the system load information is greater than the preset system load threshold, then it can be determined that the server is overloaded.

It should be noted that, if the current system load information of the server includes multiple information, and a corresponding multiple system load threshold is preset, when the current system load information of the server is compared with a preset system load threshold, if If there is a case where the comparison result is greater than greater, the server is overloaded. That is to say, if the current system load information of the server is less than or equal to the corresponding system load threshold, it is determined that the server is not overloaded. The system load information of the server is the local resource usage rate of the server, the system load threshold is the local resource usage threshold, and the local resource includes multiple local resources as an example, and the local resource usage rate is set for each local resource in advance. Threshold; after comparing the current usage rate of each local resource of the server with the corresponding local resource usage threshold, if any current local resource usage rate is greater than the corresponding local resource usage threshold, then determining The server is overloaded; if the current usage rate of each local resource is less than or equal to the corresponding local resource usage threshold, it is determined that the server is not overloaded.

204: If it is determined that the server is overloaded, the number of times the request should be rejected within the preset time period is obtained;

Specifically, after determining that the server is overloaded, the processing may be directly processed for rejection. As a preferred method, in order to avoid all requests being rejected in a short period of time, and in order to ensure that the resources of the server are utilized more, the number of times that the request should be rejected within a preset time period may be obtained after determining that the server is overloaded. The step further determines the manner in which the request to be processed is processed.

205: Determine, according to the obtained number of times that the request is rejected, whether to refuse to process the pending request;

Specifically, after obtaining the number of times that the request should be rejected within the preset time period, each time the pending request is received, the processing request that is rejected within a time period equal to the preset time period before the pending request is received may be determined. Whether the number of times has reached the number of times the request should be rejected within the preset time period, and if it has been reached, accepts the pending request and then processes it later. Otherwise, you can choose to reject or accept the pending request at random. Of course, the number of times that the processing request should be accepted within the preset time period can also be obtained. When a new pending request is received, the processing request accepted within a time period equal to the preset time period before the pending request arrives can be determined. Whether the number of times has reached the number of times the request should be accepted within the preset time period, and if it has been reached, rejects the pending request and then processes it later. Otherwise, you can choose to reject or accept the pending request at random. In this embodiment, the method for determining whether to reject the pending request is determined according to the number of times the processing request should be rejected within the preset preset time period. Of course, other methods may be used to determine whether to reject the pending request. The same is not specifically limited.

206: If it is determined to refuse to process the pending request, the processing request is rejected.

Specifically, if it is determined that the pending request is rejected, the processing request is rejected, and the rejection response is sent to the device that sends the pending request, so that the peer device can learn the processing result of the current request. Regarding the manner of sending the reject response, this embodiment does not specifically limit this.

Embodiment 3

An embodiment of the present invention provides a method for protecting an overload of a server. The method provided in this embodiment is described by taking the example of the server as an example. Referring to FIG. 3, the method process provided by this embodiment includes:

301: Receive a pending request, and obtain current system load information of the server.

Specifically, the implementation principle of the step is the same as the implementation principle of the step 201 in the second embodiment. For details, refer to the content of the step 201 in the second embodiment, and details are not described herein again.

302: Compare the current system load information of the server with a preset system load threshold;

Specifically, the system load information of the server may include a local resource usage rate of the server, and the local resource usage rate of the server may include at least one of a CPU usage rate, a memory usage rate, and a network bandwidth usage rate; correspondingly, preset The system load threshold may include a pre-set local resource usage threshold.

Specifically, the implementation principle of the step is the same as the implementation principle of the step 202 in the second embodiment. For details, refer to the content of the step 202 in the second embodiment, and details are not described herein again.

303: Determine, according to the comparison result, whether the server is overloaded;

Specifically, the implementation principle of the step is the same as the implementation principle of the step 203 in the second embodiment. For details, refer to the content of the step 203 in the second embodiment, and details are not described herein again.

304: If it is determined that the server is overloaded, obtain a random number, and determine whether the random number is the same as the preset value;

Specifically, after determining that the server is overloaded, the processing request may be directly rejected. As a preferred manner, the method provided in this embodiment further includes the step of setting a probability of rejecting the pending request, that is, a return rejection rate, to preset at least one value according to the return rejection rate, and after determining that the server is overloaded, the server may Generate a random number to determine whether the generated random number and the preset value are The same, so that the subsequent step can further determine whether to process the pending request according to the current judgment result.

For example, the probability that the server rejects the pending request is 10%, that is, the rejection rate is 10%, and the value 9 can be preset according to the rejection rate. After determining that the server has been overloaded, the server generates a random number in 0-9. And obtaining the random number, wherein the probability that the obtained random number is 9 is 10%. Certainly, the value may be preset to 0 to 9 according to the rejection rate. After determining that the server has been overloaded, the server generates a random number in 0 to 99 and obtains the random number, wherein the obtained random number is 0-9. The probability is 10%, which is not specifically limited in this embodiment.

305: Determine, according to the judgment result, whether to reject the pending request;

Specifically, when the result of the determination is that the obtained random number is the same as the preset value, it may be determined that the pending request is rejected.

For example, if the server obtains a random number of 1 from 0 to 9, and the preset value is 9, then the pending request is accepted. The obtained random number 9 and the preset value are also 9, and the pending request is rejected at this time. It should be noted that the probability of obtaining the number 9 from 0 to 9 is 10%, which is exactly the above-mentioned rejection rate.

Of course, in other embodiments, the probability of accepting the pending request may also be preset to set at least one value according to the preset probability of accepting the pending request. After determining that the server has been overloaded, the server may generate a random number to determine the generation. Whether the random number is the same as the preset value, and when the judgment result is that the obtained random number is different from the preset value, it is determined to refuse to process the pending request. For example, the preset probability of accepting the pending request is 10%, and the value 9 may be preset; after determining that the server has been overloaded, the server generates a random number in 0-9 and acquires the random number, wherein the obtained random number The probability of 9 is 10%; if the generated random number is not 9, it is determined to refuse to process the pending request. Or, the value is set to 0 to 9 in advance. After determining that the server is overloaded, the server generates a random number in 0 to 99 and obtains the random number, wherein the obtained random number is 0 to 9. The rate is 10%; if the generated random number is not 0-9, it is determined to refuse to process the pending request.

306: If it is determined that the pending request is refused to be processed, the processing request is rejected.

Specifically, the implementation principle of the step is the same as the implementation principle of the step 206 in the second embodiment. For details, refer to the content of the step 206 in the second embodiment, and details are not described herein again. In the method provided in this embodiment, since the system load information of the server is deterministic, the system load threshold can reflect the real situation of whether the server is overloaded. Therefore, the current system load information of the server is compared with a preset system load threshold. After that, according to the comparison result, it is possible to accurately determine whether the server is overloaded, thereby achieving better overload protection of the server by rejecting the processing of the processing request when determining that the server is overloaded.

Embodiment 4

The embodiment of the invention provides an overload protection device for a server, which is used for performing the overload protection method of the server provided in the first embodiment to the third embodiment. Referring to Figure 4, the apparatus includes one or more processors and a processor readable storage medium. The processor readable storage medium has a plurality of modules stored thereon, including:

The first receiving module 401 is configured to receive a pending request.

The first obtaining module 402 is configured to obtain current system load information of the server.

The first determining module 403 is configured to compare the current system load information of the server with a preset system load threshold, and determine whether the server is overloaded according to the comparison result;

The processing module 404 is configured to refuse to process the processing request when determining that the server is overloaded.

Specifically, the system load information of the server may include a local resource usage rate of the server, and the local resource usage rate of the server may include at least one of a CPU usage rate, a memory usage rate, and a network bandwidth usage rate; correspondingly, preset The system load threshold can include a preset Land resource usage threshold.

As a preferred embodiment, the first obtaining module 402 is configured to reacquire the system load information of the server when the system load information of the pre-stored server expires, and use the acquired system load information as the current system load information of the server. .

As a preferred embodiment, the first obtaining module 402 is configured to: when the system load information of the pre-stored server is not expired, read the system load information of the pre-stored server, and use the read system load information as the current server. System load information.

As a preferred embodiment, the multiple modules further include:

The first storage module is configured to pre-fetch and store system load information of the server.

As a preferred embodiment, the multiple modules further include:

a second receiving module, configured to receive a system load threshold setting command;

The second storage module is configured to set and store a system load threshold according to a system load threshold setting command.

As a preferred embodiment, the second storage module is further configured to determine whether the system load threshold setting command is legal. When determining that the system load threshold setting command is legal, the step of setting and storing the system load threshold according to the system load threshold setting command is performed.

As a preferred embodiment, the multiple modules further include:

a second obtaining module, configured to acquire a number of times that the request should be rejected within a preset time period;

a second determining module, configured to determine whether to reject the pending request according to the number of times the processing request should be rejected within the preset preset time period;

And a processing module, configured to perform a step of rejecting the processing of the processing request when determining to refuse to process the pending request.

As a preferred embodiment, the multiple modules further include:

a third obtaining module, configured to acquire a random number;

a determining module, configured to determine whether the random number is the same as the preset value;

a third determining module, configured to determine, according to the determination result, whether to reject the pending request;

In the device provided in this embodiment, since the system load information of the server is deterministic, the system load threshold can reflect the real situation of whether the server is overloaded. Therefore, by comparing the current system load information of the server with a preset system load threshold. After that, according to the comparison result, it is possible to accurately determine whether the server is overloaded, thereby achieving better overload protection of the server by rejecting the processing of the processing request when determining that the server is overloaded.

Embodiment 5

The embodiment provides an overload protection device for a server, which can be used to perform the overload protection method of the server provided in the foregoing embodiment. Referring to FIG. 5, the overload protection device 500 of the server includes:

The server's overload protection device 500 may include an RF (Radio Frequency) circuit 110, a memory 120 including one or more computer readable storage media, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, and WiFi ( Wireless Fidelity module 170, a processor 180 including one or more processing cores, and a power supply 190 and the like. It will be understood by those skilled in the art that the structure of the overload protection device 500 of the server shown in FIG. 5 does not constitute a limitation of the overload protection device 500 of the server, and may include more or less components than those illustrated, or may combine some Parts, or different parts. among them:

The RF circuit 110 can be used for transmitting and receiving information or during a call, and receiving and transmitting signals. Specifically, after receiving downlink information of the base station, the downlink information is processed by one or more processors 180. In addition, the data related to the uplink is sent to the base station. . Generally, the RF circuit 110 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier). , duplexer, etc. In addition, RF circuitry 110 can also communicate with the network and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access). , Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), e-mail, SMS (Short Messaging Service), and the like.

The memory 120 can be used to store software programs and modules, and the processor 180 executes various functional applications and data processing by running software programs and modules stored in the memory 120. The memory 120 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to The data of the server's overload protection device 500 is created (such as audio data, phone book, etc.). Moreover, memory 120 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 120 may also include a memory controller to provide access to memory 120 by processor 180 and input unit 130.

The input unit 130 can be configured to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls. Specific The input unit 130 can include a touch-sensitive surface 131 as well as other input devices 132. Touch-sensitive surface 131, also referred to as a touch display or trackpad, can collect touch operations on or near the user (such as a user using a finger, stylus, etc., on any suitable object or accessory on touch-sensitive surface 131 or The operation near the touch-sensitive surface 131) and driving the corresponding connecting device according to a preset program. Alternatively, the touch-sensitive surface 131 can include two portions of a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information. The processor 180 is provided and can receive commands from the processor 180 and execute them. In addition, the touch-sensitive surface 131 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch-sensitive surface 131, the input unit 130 can also include other input devices 132. Specifically, other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.

The display unit 140 can be used to display information input by the user or information provided to the user and various graphical user interfaces of the overload protection device 500 of the server, which can be composed of graphics, text, icons, videos, and any combination thereof. . The display unit 140 may include a display panel 141. Alternatively, the display panel 141 may be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like. Further, the touch-sensitive surface 131 may cover the display panel 141, and when the touch-sensitive surface 131 detects a touch operation thereon or nearby, it is transmitted to the processor 180 to determine the type of the touch event, and then the processor 180 according to the touch event The type provides a corresponding visual output on display panel 141. Although in FIG. 5, touch-sensitive surface 131 and display panel 141 are implemented as two separate components to implement input and input functions, in some embodiments, touch-sensitive surface 131 can be integrated with display panel 141 for input. And output function.

The server's overload protection device 500 may also include at least one type of sensor 150, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 141 according to the brightness of the ambient light, and the proximity sensor may be turned off when the overload protection device 500 of the server moves to the ear. Display panel 141 and/or backlight. As a kind of motion sensor, the gravity acceleration sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc. As for the server's overload protection device 500, other sensors such as gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc. can be configured. , will not repeat them here.

The audio circuit 160, the speaker 161, and the microphone 162 can provide an audio interface between the user and the server's overload protection device 500. The audio circuit 160 can transmit the converted electrical data of the received audio data to the speaker 161 for conversion to the sound signal output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electrical signal by the audio circuit 160. After receiving, it is converted into audio data, and then processed by the audio data output processor 180, transmitted to the overload protection device 500 such as another server via the RF circuit 110, or outputted to the memory 120 for further processing. The audio circuit 160 may also include an earbud jack to provide communication of the peripheral earphones with the server's overload protection device 500.

WiFi is a short-range wireless transmission technology, and the server's overload protection device 500 can help users to send and receive emails, browse web pages, and access streaming media through the WiFi module 170, which provides wireless broadband Internet access for users. Although FIG. 5 shows the WiFi module 170, it can be understood that it does not belong to the necessary configuration of the overload protection device 500 of the server, and can be omitted as needed within the scope of not changing the essence of the invention.

The processor 180 is the control center of the server's overload protection device 500, which connects various portions of the entire handset using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 120, and by calling stored in the memory 120. The internal data, the server's overload protection device 500's various functions and processing data, thereby overall monitoring of the mobile phone. Optionally, the processor 180 may include one or more processing cores; preferably, the processor 180 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like. The modem processor primarily handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 180.

The server's overload protection device 500 also includes a power supply 190 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically coupled to the processor 180 through a power management system to manage charging, discharging, and power consumption through the power management system. Management and other functions. Power supply 190 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.

Although not shown, the overload protection device 500 of the server may further include a camera, a Bluetooth module, and the like, and details are not described herein again. Specifically, in this embodiment, the display unit of the overload protection device 500 of the server is a touch screen display, and the overload protection device 500 of the server further includes a memory, and one or more programs, wherein one or more programs are stored in the memory, And configured to be executed by one or more processors. The one or more programs include instructions for performing the following operations:

If it is determined that the server is overloaded, the processing request is rejected.

It is assumed that the above is the first possible implementation manner, and in the second possible implementation manner provided by the first possible implementation manner, the memory of the overload protection device 500 of the server is further included for performing the following Operation instructions:

In a third possible implementation provided by the first possible implementation, the memory of the overload protection device 500 of the server further includes instructions for performing the following operations:

In a fourth possible implementation manner provided by any one of the second or third possible implementation manners, the memory of the overload protection device 500 of the server further includes the following operations. instruction:

Pre-fetch and store the system load information of the server.

In a fifth possible implementation manner provided by the first possible implementation manner, the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:

In a sixth possible implementation manner provided by the fifth possible implementation manner, the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:

Determine whether the system load threshold setting command is legal;

In a seventh possible implementation manner provided by the first possible implementation manner, the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:

Obtaining the number of times the request should be rejected within the preset time period, and determining whether to reject the pending request according to the number of times the request should be rejected within the preset time period obtained;

In an eighth possible implementation manner provided by the first possible implementation manner, the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:

The overload protection device 500 of the server provided by the present invention, because the system load information of the server is deterministic, the system load threshold can reflect the real situation of whether the server is overloaded, and therefore, the current system load information of the server and the preset system load are After the thresholds are compared, it is possible to accurately determine whether the server is overloaded according to the comparison result, thereby performing better overload protection on the server by rejecting the processing of the processing request when determining that the server is overloaded.

Embodiment 6

The embodiment of the present invention further provides a computer readable storage medium, which may be a computer readable storage medium included in the memory in the above embodiment; or may exist separately and not assembled into the terminal. Computer readable storage medium. Computer readable storage medium One or more programs are stored, and the one or more programs are used by one or more processors to execute a permission query method for implementing multidimensional data, the method comprising:

Assume that the above is the first possible implementation manner, in the second possible implementation manner provided by the first possible implementation manner, the acquiring the current system load information of the server includes:

In a third possible implementation manner provided by the first possible implementation manner, the acquiring current system load information of the server includes:

In a fourth possible implementation manner provided by the second or the third possible implementation manner, before the acquiring the current system load information of the server, the method further includes:

Pre-fetch and store the system load information of the server.

In a fifth possible implementation provided by the first possible embodiment as a basis, Before comparing the current system load information of the server with a preset system load threshold, the method further includes:

In a sixth possible implementation manner provided by the fifth possible implementation manner, after the receiving the system load threshold setting command, the method further includes:

Determine whether the system load threshold setting command is legal;

In a seventh possible implementation manner provided by the first possible implementation manner, before the refusing to process the to-be-processed request, the method further includes:

In an eighth possible implementation manner provided by the first possible implementation manner, before the refusing to process the to-be-processed request, the method further includes:

The computer readable storage medium provided by the embodiment of the present invention, because the system load information of the server is deterministic, the system load threshold can reflect the real situation of whether the server is overloaded, and therefore, the current system load information of the server and the preset system are After the load thresholds are compared, it is possible to accurately determine whether the server is overloaded according to the comparison result, thereby determining the server overload. Better handling of the server is achieved by refusing to process the request.

Example 7

Embodiments of the present invention provide a graphical user interface for use on a terminal, the terminal including a touch screen display, a memory, and one or more processors for executing one or more programs; The graphical user interface includes:

The graphical user interface provided by the embodiment of the present invention, because the system load information of the server is deterministic, the system load threshold can reflect the real situation of whether the server is overloaded. Therefore, by setting the current system load information of the server and the preset system load threshold. After the comparison, the server can accurately determine whether the server is overloaded according to the comparison result, so that when the server is overloaded, the server can be processed by rejecting the processing request, thereby achieving better overload protection for the server.

It should be noted that the overload protection device of the server provided by the foregoing embodiment is only illustrated by the division of each functional module in the overload protection of the server. In actual applications, the foregoing functions may be assigned differently according to requirements. The functional module is completed, that is, the internal structure of the device Divided into different functional modules to complete all or part of the functions described above. In addition, the overload protection device of the server provided by the foregoing embodiment is the same as the embodiment of the overload protection method of the server. For the specific implementation process, refer to the method embodiment, and details are not described herein again.

The serial numbers of the embodiments of the present invention are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

A method for overload protection of a server, the method comprising:

Receiving a pending request and obtaining current system load information of the server;

Comparing the current system load information of the server with a preset system load threshold, and determining whether the server is overloaded according to the comparison result;

If it is determined that the server is overloaded, the processing of the pending request is refused.
The method according to claim 1, wherein the obtaining current system load information of the server comprises:

When the system load information of the server that is pre-stored expires, the system load information of the server is re-acquired, and the acquired system load information is used as the current system load information of the server.
The method according to claim 1, wherein the obtaining current system load information of the server comprises:

When the system load information of the server stored in advance is not expired, the system load information of the server stored in advance is read, and the read system load information is used as the current system load information of the server.
The method according to claim 2 or 3, wherein before the obtaining the current system load information of the server, the method further comprises:

Pre-fetch and store the system load information of the server.
The method according to claim 1, wherein before the comparing the current system load information of the server with a preset system load threshold, the method further includes:

A system load threshold setting command is received, and a system load threshold is set and stored according to the system load threshold setting command.
The method according to claim 5, further comprising: after receiving the system load threshold setting command, further comprising:

Determining whether the system load threshold setting command is legal;

If it is determined that the system load threshold setting command is legal, the step of setting and storing the system load threshold according to the system load threshold setting command is performed.
The method according to claim 1, wherein before the refusing to process the pending request, the method further comprises:

Obtaining the number of times the request should be rejected within the preset time period, and determining whether to reject the pending request according to the obtained number of times of rejecting the processing request;

If it is determined that the pending request is refused to be processed, the step of rejecting the processing of the pending request is performed.
The method according to claim 1, wherein before the refusing to process the pending request, the method further comprises:

Obtaining a random number and determining whether the random number is the same as the preset value;

Determining whether to refuse to process the pending request according to the judgment result;

If it is determined that the pending request is refused to be processed, performing a rejection of the pending request The steps.
The method according to claim 1, wherein the system load information of the server comprises a local resource usage rate of the server;

The obtaining the current system load information of the server includes: acquiring a current local resource usage rate of the server;

Comparing the current system load information of the server with a preset system load threshold, and determining whether the server is overloaded according to the comparison result includes: setting a current local resource usage rate of the server with a preset The local resource usage thresholds are compared, and it is determined whether the server is overloaded according to the comparison result.
The method according to claim 9, wherein the local resource comprises a plurality of local resources.

The comparing the current local resource usage rate of the server with a preset local resource usage threshold, and determining whether the server is overloaded according to the comparison result includes:

Comparing the current usage rate of each local resource of the server with a preset usage threshold of each local resource;

If the current usage rate of all the local resources is less than the corresponding preset local resource usage threshold, it is determined that the server is not overloaded;

If the current usage rate of any one of the local resources is greater than the corresponding preset local resource usage threshold, the server is determined to be overloaded.
An overload protection device for a server, characterized in that the device comprises a processor and The processor readable storage medium stores a plurality of modules, the plurality of modules including:

a first receiving module, configured to receive a pending request;

a first acquiring module, configured to acquire current system load information of the server;

a first determining module, configured to compare the current system load information of the server with a preset system load threshold, and determine whether the server is overloaded according to the comparison result;

And a processing module, configured to refuse to process the to-be-processed request when determining that the server is overloaded.
The device according to claim 11, wherein the obtaining module is configured to re-acquire system load information of the server when the system load information of the server stored in advance expires, and acquire the system The load information is used as current system load information of the server.
The device according to claim 11, wherein the obtaining module is configured to: when pre-stored system load information of the server is not expired, read pre-stored system load information of the server, and The read system load information is used as the current system load information of the server.
The device according to claim 12 or 13, wherein the plurality of modules further comprises:

The first storage module is configured to pre-fetch and store system load information of the server.
The device according to claim 11, wherein the plurality of modules further comprises:

a second receiving module, configured to receive a system load threshold setting command;

And a second storage module, configured to set and store a system load threshold according to the system load threshold setting command.
The device according to claim 15, wherein the second storage module is further configured to determine whether the system load threshold setting command is legal; when it is determined that the system load threshold setting command is legal, performing according to the The system load threshold setting command sets and stores the system load threshold.
The device according to claim 11, wherein the plurality of modules further comprises:

a second obtaining module, configured to acquire a number of times that the request should be rejected within a preset time period;

a second determining module, configured to determine, according to the number of times the processing request should be rejected within the preset preset time period, whether to refuse to process the pending request;

The processing module is configured to perform a step of rejecting processing of the to-be-processed request when determining to refuse to process the to-be-processed request.
The device according to claim 11, wherein the plurality of modules further comprises:

a third obtaining module, configured to acquire a random number;

a determining module, configured to determine whether the random number is the same as a preset value;

a third determining module, configured to determine, according to the determination result, whether to reject the pending request;

The processing module is configured to perform a step of rejecting processing of the to-be-processed request when determining to refuse to process the to-be-processed request.