WO2015090248A1 - Procédé et dispositif de protection contre la surcharge d'un serveur - Google Patents

Procédé et dispositif de protection contre la surcharge d'un serveur Download PDF

Info

Publication number
WO2015090248A1
WO2015090248A1 PCT/CN2015/073012 CN2015073012W WO2015090248A1 WO 2015090248 A1 WO2015090248 A1 WO 2015090248A1 CN 2015073012 W CN2015073012 W CN 2015073012W WO 2015090248 A1 WO2015090248 A1 WO 2015090248A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
system load
load information
request
preset
Prior art date
Application number
PCT/CN2015/073012
Other languages
English (en)
Chinese (zh)
Inventor
苏士杰
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2015090248A1 publication Critical patent/WO2015090248A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5022—Workload threshold

Definitions

  • the present invention relates to the field of Internet technologies, and in particular, to a server overload protection method and apparatus.
  • the embodiment of the invention provides a method and device for overload protection of a server.
  • the technical solution is as follows:
  • a method for overload protection of a server comprising:
  • an overload protection device for a web server 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
  • a processing module configured to refuse to process the to-be-processed request when determining that the server is overloaded.
  • 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.
  • FIG. 1 is a flowchart of a method for overload protection of a server according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for overload protection of a server according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of a method for overload protection of a server according to Embodiment 3 of the present invention.
  • FIG. 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.
  • the embodiment of the present invention provides a method for overload protection of a server.
  • 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:
  • the current system load information of the server is obtained, including but not limited to:
  • 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.
  • obtaining current system load information of the server including but not limited to:
  • the system load information of the pre-stored server 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.
  • the method further includes:
  • the method further includes:
  • the step of setting and storing the system load threshold according to the system load threshold setting command is performed.
  • the step of rejecting the processing of the processing request is performed.
  • the step of rejecting the processing of the processing request is performed.
  • 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.
  • 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:
  • 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
  • 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.
  • the memory on the server is 8 GB.
  • 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 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:
  • 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;
  • determining whether the system load information of the pre-stored server is expired may be as follows:
  • the system load information of the server 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.
  • 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.
  • the system load information of the pre-stored 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the system load threshold is a local resource usage threshold.
  • 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:
  • the system load threshold setting command may adopt a URL (Uniform Resource Locator) format.
  • 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.
  • the system load information includes multiple types of information
  • 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.
  • 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.
  • the system load threshold setting command may be determined to be legal after receiving the system load threshold setting command.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the current system load information of the server is less than or equal to the preset system load threshold.
  • the server overload may be determined. If the comparison result is the second type, it may be determined that the server is not overloaded.
  • the pre-set system load threshold is 90% CPU usage and 80% memory usage.
  • 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.
  • 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.
  • the processing may be directly processed for rejection.
  • 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.
  • 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.
  • 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.
  • 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.
  • this embodiment does not specifically limit this.
  • 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.
  • 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:
  • the implementation principle of the step is the same as the implementation principle of the step 201 in the second embodiment.
  • the implementation principle of the step 201 in the second embodiment refers to the content of the step 201 in the second embodiment, and details are not described herein again.
  • 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.
  • the implementation principle of the step is the same as the implementation principle of the step 202 in the second embodiment.
  • the implementation principle of the step 202 in the second embodiment refers to the content of the step 202 in the second embodiment, and details are not described herein again.
  • the implementation principle of the step is the same as the implementation principle of the step 203 in the second embodiment.
  • the implementation principle of the step 203 in the second embodiment refers to the content of the step 203 in the second embodiment, and details are not described herein again.
  • the processing request may be directly rejected.
  • 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.
  • the probability that the server rejects the pending request is 10%, that is, the rejection rate is 10%
  • 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%.
  • 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.
  • 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.
  • 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.
  • the probability of obtaining the number 9 from 0 to 9 is 10%, which is exactly the above-mentioned rejection rate.
  • 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.
  • 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.
  • the preset probability of accepting the pending request is 10%
  • 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.
  • the value is set to 0 to 9 in advance.
  • the server 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.
  • the implementation principle of the step is the same as the implementation principle of the step 206 in the second embodiment.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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. .
  • 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.
  • the multiple modules further include:
  • the first storage module is configured to pre-fetch and store system load information of the server.
  • 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.
  • 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.
  • 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
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • RF Radio Frequency
  • 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. .
  • 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.
  • 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.
  • GSM Global System of Mobile communication
  • GPRS General Packet Radio Service
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • e-mail Short Messaging Service
  • 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.).
  • 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.
  • 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.
  • the touch-sensitive surface 131 can include two portions of a touch detection device and a touch controller.
  • 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.
  • the touch-sensitive surface 131 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 130 can also include other input devices 132.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the server's overload protection device 500 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.
  • 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
  • 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.
  • 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 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.
  • a power supply 190 (such as a battery) that supplies power to various components.
  • 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.
  • 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.
  • the display unit of the overload protection device 500 of the server is a touch screen display
  • 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:
  • 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.
  • 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.
  • the memory of the overload protection device 500 of the server further includes instructions for performing the following operations:
  • the system load information of the pre-stored server 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.
  • the memory of the overload protection device 500 of the server further includes the following operations. instruction:
  • the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:
  • the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:
  • the step of setting and storing the system load threshold according to the system load threshold setting command is performed.
  • the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:
  • the step of rejecting the processing of the processing request is performed.
  • the memory of the overload protection device 500 of the server further includes an instruction for performing the following operations:
  • the step of rejecting the processing of the processing request is performed.
  • 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.
  • 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:
  • 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.
  • the acquiring the current system load information of the server includes:
  • 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.
  • the acquiring current system load information of the server includes:
  • the system load information of the pre-stored server 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.
  • the method before the acquiring the current system load information of the server, the method further includes:
  • the method Before comparing the current system load information of the server with a preset system load threshold, the method further includes:
  • the method further includes:
  • the step of setting and storing the system load threshold according to the system load threshold setting command is performed.
  • the method before the refusing to process the to-be-processed request, the method further includes:
  • the step of rejecting the processing of the processing request is performed.
  • the method before the refusing to process the to-be-processed request, the method further includes:
  • the step of rejecting the processing of the processing request is performed.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un dispositif de protection contre la surcharge d'un serveur. Le procédé comprend les étapes suivantes : une demande à traiter est reçue et des informations de charge de système actuel de serveur sont obtenues (101); les informations de charge de système actuel de serveur sont comparées à un seuil de charge de système et, en fonction du résultat de la comparaison, on détermine que le serveur est surchargé (102); et si on a déterminé que le serveur est surchargé, le traitement de la demande à traiter est refusé (103). Le dispositif comprend : un premier module de réception (401), un premier module d'obtention (402), un premier module de détermination (403) et un module de traitement (404). Du fait de la certitude des informations de charge du système du serveur, la situation de surcharge vraie du serveur peut être reflétée. En conséquence, la comparaison des informations de charge de système actuel de serveur obtenues avec le seuil de charge de système, et le refus de traiter la demande à traiter lorsqu'on a déterminé, en fonction du résultat de la comparaison, que le serveur est surchargé, permet de déterminer précisément si le serveur est surchargé, ce qui permet d'effectuer une meilleure protection du serveur.
PCT/CN2015/073012 2013-12-16 2015-02-13 Procédé et dispositif de protection contre la surcharge d'un serveur WO2015090248A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310693053.1A CN104142862B (zh) 2013-12-16 2013-12-16 服务器的过载保护方法及装置
CN201310693053.1 2013-12-16

Publications (1)

Publication Number Publication Date
WO2015090248A1 true WO2015090248A1 (fr) 2015-06-25

Family

ID=51852043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/073012 WO2015090248A1 (fr) 2013-12-16 2015-02-13 Procédé et dispositif de protection contre la surcharge d'un serveur

Country Status (2)

Country Link
CN (1) CN104142862B (fr)
WO (1) WO2015090248A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109918196A (zh) * 2019-01-23 2019-06-21 深圳壹账通智能科技有限公司 系统资源分配方法、装置、计算机设备和存储介质
CN110674060A (zh) * 2019-09-06 2020-01-10 平安普惠企业管理有限公司 服务的熔断控制方法及装置
CN111356903A (zh) * 2019-01-25 2020-06-30 深圳市大疆创新科技有限公司 视觉定位方法、装置及系统
CN113765687A (zh) * 2020-06-05 2021-12-07 网联清算有限公司 服务器的故障报警方法、装置、设备及存储介质
CN114326430A (zh) * 2022-01-07 2022-04-12 康体佳智能科技（深圳）有限公司 负载控制方法、装置、设备与计算机可读存储介质
US11340956B2 (en) 2020-09-11 2022-05-24 Toyota Motor Engineering & Manufacturing North America, Inc. Systems and methods for dynamic prediction and optimization of edge server scheduling
CN115150460A (zh) * 2022-06-30 2022-10-04 济南浪潮数据技术有限公司 一种节点安全注册方法、装置、设备及可读存储介质

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104142862B (zh) * 2013-12-16 2015-09-16 腾讯科技（深圳）有限公司 服务器的过载保护方法及装置
CN106302570A (zh) * 2015-05-14 2017-01-04 阿里巴巴集团控股有限公司 一种请求处理方法及装置
CN105554049B (zh) * 2015-08-14 2018-12-25 广州爱九游信息技术有限公司 分布式业务量控制方法和装置
CN105376332A (zh) * 2015-12-14 2016-03-02 江苏名通信息科技有限公司 一种用于手机游戏服务器的负荷迁徙方法
CN107092526B (zh) * 2016-11-02 2021-06-15 北京星选科技有限公司 任务处理方法及装置
CN107465627A (zh) * 2017-08-11 2017-12-12 北京小度信息科技有限公司 过载保护方法、装置、电子设备及流量处理系统
CN108509148B (zh) * 2018-02-07 2021-08-06 新华三技术有限公司 一种i/o请求处理方法以及装置
CN110933122B (zh) * 2018-09-20 2023-06-23 北京默契破冰科技有限公司 管理服务器的方法、设备和计算机存储介质
CN109726003B (zh) * 2019-01-04 2020-09-15 Oppo广东移动通信有限公司 应用解冻的处理方法、电子装置及计算机可读存储介质
CN111988234A (zh) * 2019-05-23 2020-11-24 厦门网宿有限公司 过载保护方法、装置、服务器及存储介质
CN110502345A (zh) * 2019-08-26 2019-11-26 北京博睿宏远数据科技股份有限公司 一种过载保护方法、装置、计算机设备及存储介质
CN111984437A (zh) * 2020-08-31 2020-11-24 平安医疗健康管理股份有限公司 Drg分组服务器rpc服务处理方法、装置和计算机设备
CN112559189A (zh) * 2020-12-21 2021-03-26 厦门亿联网络技术股份有限公司 业务请求的处理方法、装置、电子设备及存储介质
CN113051079B (zh) * 2021-03-31 2022-03-01 淄博职业学院 一种计算机过载保护装置
CN115801684B (zh) * 2023-01-31 2023-04-21 深圳方位通讯科技有限公司 一种基于ssh服务器的终端交互方法及系统

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009648A (zh) * 2006-12-27 2007-08-01 北京航空航天大学 多服务器的分层迭代负载平衡方法
US20080154805A1 (en) * 2006-12-20 2008-06-26 Nagasubramanian Gurumoorthy Utilization based installation on a computing system
CN102708011A (zh) * 2012-05-11 2012-10-03 南京邮电大学 一种面向云计算平台任务调度的多级负载评估方法
TW201308097A (zh) * 2011-08-02 2013-02-16 Viaccess Sa 用於平穩一伺服器之工作負載之方法
CN103036994A (zh) * 2012-12-18 2013-04-10 曙光信息产业(北京)有限公司 实现负载均衡的云存储系统
CN103188345A (zh) * 2013-03-01 2013-07-03 北京邮电大学 分布式动态负载管理系统和方法
CN104142862A (zh) * 2013-12-16 2014-11-12 腾讯科技（深圳）有限公司 服务器的过载保护方法及装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080154805A1 (en) * 2006-12-20 2008-06-26 Nagasubramanian Gurumoorthy Utilization based installation on a computing system
CN101009648A (zh) * 2006-12-27 2007-08-01 北京航空航天大学 多服务器的分层迭代负载平衡方法
TW201308097A (zh) * 2011-08-02 2013-02-16 Viaccess Sa 用於平穩一伺服器之工作負載之方法
CN102708011A (zh) * 2012-05-11 2012-10-03 南京邮电大学 一种面向云计算平台任务调度的多级负载评估方法
CN103036994A (zh) * 2012-12-18 2013-04-10 曙光信息产业(北京)有限公司 实现负载均衡的云存储系统
CN103188345A (zh) * 2013-03-01 2013-07-03 北京邮电大学 分布式动态负载管理系统和方法
CN104142862A (zh) * 2013-12-16 2014-11-12 腾讯科技（深圳）有限公司 服务器的过载保护方法及装置

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109918196A (zh) * 2019-01-23 2019-06-21 深圳壹账通智能科技有限公司 系统资源分配方法、装置、计算机设备和存储介质
CN109918196B (zh) * 2019-01-23 2022-11-29 深圳壹账通智能科技有限公司 系统资源分配方法、装置、计算机设备和存储介质
CN111356903A (zh) * 2019-01-25 2020-06-30 深圳市大疆创新科技有限公司 视觉定位方法、装置及系统
CN110674060A (zh) * 2019-09-06 2020-01-10 平安普惠企业管理有限公司 服务的熔断控制方法及装置
CN113765687A (zh) * 2020-06-05 2021-12-07 网联清算有限公司 服务器的故障报警方法、装置、设备及存储介质
CN113765687B (zh) * 2020-06-05 2023-08-01 网联清算有限公司 服务器的故障报警方法、装置、设备及存储介质
US11340956B2 (en) 2020-09-11 2022-05-24 Toyota Motor Engineering & Manufacturing North America, Inc. Systems and methods for dynamic prediction and optimization of edge server scheduling
CN114326430A (zh) * 2022-01-07 2022-04-12 康体佳智能科技（深圳）有限公司 负载控制方法、装置、设备与计算机可读存储介质
CN115150460A (zh) * 2022-06-30 2022-10-04 济南浪潮数据技术有限公司 一种节点安全注册方法、装置、设备及可读存储介质

Also Published As

Publication number Publication date
CN104142862B (zh) 2015-09-16
CN104142862A (zh) 2014-11-12

Similar Documents

Publication Publication Date Title
WO2015090248A1 (fr) Procédé et dispositif de protection contre la surcharge d'un serveur
US10831161B2 (en) Method and device for sending communication message
US10304461B2 (en) Remote electronic service requesting and processing method, server, and terminal
CN104518953B (zh) 删除消息的方法、即时通信终端及系统
WO2016150270A1 (fr) Procédé et appareil pour traiter un message de session de groupe
CN104852885B (zh) 一种进行验证码验证的方法、装置和系统
WO2017096909A1 (fr) Procédé et appareil d'établissement de connexion de données
CN104065693A (zh) 一种网页应用中网络数据的访问方法、装置和系统
US10237291B2 (en) Session processing method and device, server and storage medium
CN109039989B (zh) 地址解析协议欺骗检测方法、主机及计算机可读存储介质
WO2014032559A1 (fr) Procédé et dispositif pour le téléchargement d'un fichier vers l'aval
WO2023236972A1 (fr) Procédé et appareil d'avertissement de sécurité environnementale de communication, dispositif terminal et support de stockage
CN107317828B (zh) 文件下载方法及装置
US20140344423A1 (en) Method, apparatus and system for switching function mode
CN115118636B (zh) 网络抖动状态的确定方法、装置、电子设备及存储介质
CN113613310A (zh) Wifi连接方法、装置、存储介质及移动终端
US20140366094A1 (en) Communication method, communication apparatus and terminal
CN110913022A (zh) 移动终端网络文件下载方法、装置、系统及存储介质
CN106445841B (zh) 一种数据传输控制方法和装置
CN114095585B (zh) 数据传输方法、装置、存储介质及电子设备
CN114189436B (zh) 一种多集群配置部署方法、装置、电子设备和存储介质
CN111405649B (zh) 一种信息传输方法、装置及移动终端
CN116684467B (zh) 数据获取方法、电子设备及存储介质
CN107276880B (zh) 一种获取邮件的方法和装置
CN117112153A (zh) 任务处理方法、装置、计算机设备及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15729730

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC , EPO FORM 1205A DATED 31-10-16

122 Ep: pct application non-entry in european phase

Ref document number: 15729730

Country of ref document: EP

Kind code of ref document: A1