Request processing optimization method and computer readable storage medium

Abstract

The invention discloses a request processing optimization method and a computer readable storage medium. The method comprises the following steps: creating a first-in first-out queue and a first-in second-out queue; when the server has a request timeout condition or reaches an upper limit of a task processing quantity, obtaining a CPU occupancy rate or a message processing speed of equipment wherethe server is located; if the CPU occupancy rate does not reach a preset first threshold value or the message processing speed reaches a preset second threshold value, writing the received task message into the first-in first-out queue; and if the CPU occupancy rate reaches a preset first threshold or the message processing speed does not reach a preset second threshold, writing the received taskmessage into the first-in last-out queue. The request success rate can be improved.

Description

technical field [0001] The invention relates to the technical field of the Internet, in particular to a request processing optimization method and a computer-readable storage medium. Background technique [0002] In many projects, there are two parts, the client and the server, and the server actually has many different architecture implementation methods, one of which is the microservice architecture method, which is mainly reflected in the request access between the gateway and the microservice and Aggregation interface and other operations. [0003] The implementation of the above architecture is mainly the gateway calls microservices, and the mutual calls between microservices. In fact, the interfaces provided by each microservice have an upper limit on the number of requests or resources. When the microservice request reaches the upper limit, or other special circumstances, such as machine resources or network jitter, etc., there will be microservices. At this time, t...

AI Technical Summary

Problems solved by technology

In fact, the interfaces provided by each microservice have an upper limit on the number of requests or resources. When the microservice request reaches the upper limit, or other special circumstances, such as machine resources or network jitter, etc., there will be microservices. At this time, the method adopted by the current existing system is generally to set a timeout period for processing, and when the timeout period is reached, the message will be discarded

Once congestion occurs, other requests will continue to be congested, resulting in the unavailability of the entire microservice system

Or a more advanced system, when this happens, the queue is used to store task messages. The queue is a first-in-first-out queue, and the advanced messages are processed first. Therefore, it will take a lot of time to process the late messages, which may cause The timeout was abandoned, causing the request to fail

Images