Business processing method and related device

Abstract

The application discloses a service processing method, comprising: starting a load monitor when receiving a service processing instruction; collecting current resource utilization by using the load monitor; if the current resource utilization exceeds a preset threshold, skipping a service thread provided with an annotation identifier and executing a service thread not provided with the annotation identifier; and if the current resource utilization does not exceed the preset threshold, executing all service threads. By using the technical scheme provided by the application, system resources can be flexibly allocated when system load pressure is high, thereby ensuring normal operation of services. The application also discloses a service processing device, an electronic device and a computer readable storage medium, which also have the above technical effects.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a business processing method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] Storage management software integrates all necessary operations for storage resource management, monitoring, reporting, tiered storage, performance management, disaster recovery, and business continuity. It typically uses a B / S (Browser / Server) architecture. The management software provides REST interfaces. When the frequency of external interface calls is low, the management software will not excessively consume system resources (such as CPU and memory). However, if the server system load is high, and the frequency of concurrent external REST interface calls is also high, the management software will have many threads processing simultaneously, consuming significant amounts of CPU or memory, which will affect the normal operation of core storage services. Clearly, the core storage services are more important than the management software itself. Therefore, it is necessary to limit the CPU and memory usage of the management software as much as possible to ensure stable business operation.

[0003] Therefore, how to flexibly allocate system resources when the system load is high, so as to ensure the normal operation of business, is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] The purpose of this application is to provide a business processing method that can flexibly allocate system resources when the system load is high, thereby ensuring the normal operation of the business; another purpose of this application is to provide a business processing device, electronic device, and computer-readable storage medium, all of which have the above-mentioned beneficial effects.

[0005] Firstly, this application provides a business processing method, including:

[0006] When a business processing instruction is received, the load monitor is activated;

[0007] The current resource utilization rate is obtained by using the load monitor.

[0008] If the current resource utilization rate exceeds the preset threshold, the business threads with annotations are skipped, and the business threads without annotations are executed.

[0009] If the current resource utilization rate does not exceed the preset threshold, then all business threads are executed.

[0010] Optionally, skipping business threads marked with annotations includes:

[0011] When the annotation of the business thread is marked as a blocking flag, the business thread is suspended.

[0012] When the annotation of the business thread is an interrupt flag, skip the business thread and return no response information about the business thread.

[0013] Optionally, the business processing method further includes:

[0014] When a wake-up command is received for a business thread that has the blocking flag set, the business thread is executed.

[0015] Optionally, the business processing method further includes:

[0016] Calculate the suspension duration of the suspended business threads;

[0017] When the suspension time reaches the preset time, the wake-up command is responded to.

[0018] Optionally, the business processing method further includes:

[0019] When the current resource utilization rate does not exceed the preset threshold, the wake-up command is responded to.

[0020] Optionally, obtaining the current resource utilization rate using the load monitor includes:

[0021] The load monitor is used to collect the current resource utilization rate at preset time intervals.

[0022] Optionally, the current resource utilization rate includes the current CPU utilization rate and the current memory utilization rate.

[0023] Secondly, this application also discloses a business processing apparatus, comprising:

[0024] The startup module is used to start the load monitor when a business processing instruction is received;

[0025] The data acquisition module is used to acquire the current resource utilization rate using the load monitor.

[0026] The first execution module is used to skip the business threads with annotations set if the current resource utilization rate exceeds a preset threshold, and execute the business threads without the annotations set.

[0027] The second execution module is used to execute all business threads if the current resource utilization rate does not exceed the preset threshold.

[0028] Thirdly, this application also discloses an electronic device, comprising:

[0029] Memory, used to store computer programs;

[0030] A processor for executing the computer program to implement any of the business processing methods described above.

[0031] Fourthly, this application also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the business processing methods described above.

[0032] The business processing method provided in this application includes: when a business processing instruction is received, starting a load monitor; using the load monitor to collect and obtain the current resource utilization rate; if the current resource utilization rate exceeds a preset threshold, skipping business threads with annotations and executing business threads without annotations; if the current resource utilization rate does not exceed the preset threshold, executing all business threads.

[0033] By applying the technical solution provided in this application, annotations are pre-assigned to business processes with lower importance within the system, and the business request processing mechanism is optimized. When executing business processes, the current system load is determined by assessing the current resource utilization. If the current resource utilization is high, it indicates a heavy system load. In this case, business threads with annotations can be skipped, and only those without annotations can be executed. This prioritizes higher-importance business threads, while delaying or ignoring lower-importance threads. Conversely, if the current resource utilization is low, it indicates a light system load, and all business threads can be executed sequentially without distinguishing their importance. This allows for flexible allocation of system resources, effectively ensuring the normal operation of business processes. Furthermore, this implementation requires only minor modifications to existing system code, exhibiting low invasiveness and high portability.

[0034] The business processing apparatus, electronic equipment, and computer-readable storage medium provided in this application all have the aforementioned beneficial effects, which will not be elaborated further here. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the prior art and the embodiments of this application, the accompanying drawings used in the description of the prior art and the embodiments of this application will be briefly introduced below. Of course, the accompanying drawings described below with respect to the embodiments of this application are only a part of the embodiments in this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort, and such other drawings also fall within the protection scope of this application.

[0036] Figure 1A flowchart illustrating a business processing method provided in this application;

[0037] Figure 2 A schematic diagram of the structure of a business processing device provided in this application;

[0038] Figure 3 This is a schematic diagram of the structure of an electronic device provided in this application. Detailed Implementation

[0039] The core of this application is to provide a business processing method that can flexibly allocate system resources when the system load is high, thereby ensuring the normal operation of the business. Another core aspect of this application is to provide a business processing device, electronic device, and computer-readable storage medium, all of which have the aforementioned beneficial effects.

[0040] To provide a clearer and more complete description of the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0041] This application provides a business processing method.

[0042] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a business processing method provided in this application, which may include the following steps S101 to S104.

[0043] S101: When a service processing instruction is received, the load monitor is activated;

[0044] This step aims to launch the load monitor based on business processing commands. The load monitor is used to collect the current resource utilization within the system.

[0045] Specifically, when a business processing instruction is received, the load monitor can be started. The business processing instruction refers to the instruction to start business processing within the system. Based on the business processing instruction, the execution of the corresponding business within the system can be started. The business processing instruction can be initiated by the user through the front-end device, or it can be automatically responded to by pre-set trigger conditions (such as timed conditions). Therefore, this application does not limit the method of obtaining it.

[0046] In addition, the load monitor is a pre-installed monitoring device in the system used to collect data on the utilization of resources within the system. When a business processing instruction is received, the load monitor is activated simultaneously.

[0047] S102: Obtain the current resource utilization rate using the load monitor;

[0048] This step aims to collect the current resource utilization rate within the system. After the load monitor is started, it can be used to collect the current resource utilization rate within the system. The resources referred to in the current resource utilization rate refer to various resources within the system used for business processing. Their specific types do not affect the implementation of this technical solution, and this application does not limit them. For example, in one possible implementation, the current resource utilization rate may include the current CPU utilization rate and the current memory utilization rate.

[0049] It should be noted that the purpose of using the load monitor to collect the current resource utilization rate within the system is to determine the current system load pressure. When the current resource utilization rate is high, it indicates that the current system load pressure is high and system resource scheduling is required; when the current resource utilization rate is low, it indicates that the current system load pressure is low and system resource scheduling is not required.

[0050] The current resource utilization rate can be determined by comparing it with a preset threshold (i.e., the preset threshold below). If the current resource utilization rate exceeds the preset threshold, it means that the current resource utilization rate is high. If the current resource utilization rate does not exceed the preset threshold, it means that the current resource utilization rate is low.

[0051] As mentioned above, the current resource utilization rate can include the current CPU utilization rate and the current memory utilization rate. The preset threshold can then include a threshold corresponding to the current CPU utilization rate and a threshold corresponding to the current memory utilization rate. Furthermore, when either the current CPU utilization rate exceeds its corresponding threshold, the current resource utilization rate is determined to be high; when neither exceeds its corresponding threshold, the current resource utilization rate is determined to be low. Of course, this determination method can also be used when there are many types of resources.

[0052] It is understood that the specific value of the above-mentioned preset threshold does not affect the implementation of this technical solution. Furthermore, the thresholds corresponding to different types of resources may be the same or different, and can be set by technical personnel according to the characteristics of the system itself. This application does not limit this.

[0053] S103: If the current resource utilization rate exceeds the preset threshold, skip the business threads with annotations and execute the business threads without annotations.

[0054] This step aims to handle business processes under high system load. As mentioned above, when the current resource utilization exceeds a preset threshold, it indicates a high system load, requiring system resource scheduling. Therefore, for business threads requiring processing, we first check if they have pre-set annotations. If an annotation is set, the thread's importance is relatively low, and it can be skipped. Conversely, if no annotation is set, the thread's importance is relatively high, and it should be processed directly. For skipped threads, we can later determine whether to continue processing based on the actual situation.

[0055] Within the system, each business thread can be pre-labeled with annotations based on its importance. Specifically, less important business threads are labeled with annotations, while more important threads are not. The importance of a business thread is determined by the actual business requirements of the system.

[0056] Generally, in actual development, the setting of annotation tags can follow the following two principles:

[0057] (1) Avoid setting annotations in business threads with high importance; the impact of requesting to skip business threads should be acceptable.

[0058] (2) Select appropriate business threads to set annotation markers. The appropriate criterion is that the two business threads are not closely related and skipping between them will not cause adverse results. These appropriate locations are called safepoints. Taking business threads A and B as an example, if business thread B is not executed after business thread A is executed, it will cause adverse consequences (such as unreleased resources, memory leaks, etc.). Therefore, it is not recommended to set annotation markers on business thread B. On the contrary, business thread B can be called a safepoint and annotation markers can be set.

[0059] S104: If the current resource utilization rate does not exceed the preset threshold, then execute all business threads.

[0060] This step aims to handle business processes under low system load conditions. As mentioned above, when the current resource utilization does not exceed the preset threshold, it indicates that the current system load is low, and no system resource scheduling is required. Based on this, business threads that need to be processed within the system can be executed sequentially.

[0061] As can be seen, the business processing method provided in this application pre-marks low-importance business processes within the system with annotations and optimizes the business request processing mechanism. When executing business processes, the current system load is determined by assessing the current resource utilization rate. If the current resource utilization rate is high, it indicates a heavy system load. In this case, business threads marked with annotations can be skipped, and only those without annotations can be executed. That is, high-importance business threads are prioritized, while low-importance business threads are either deferred or not processed. Conversely, if the current resource utilization rate is low, it indicates a light system load, and all business threads within the system can be executed sequentially without distinguishing their importance. This achieves flexible allocation of system resources, effectively ensuring the normal operation of business processes. Furthermore, this implementation requires only minor modifications to existing system code, exhibiting low invasiveness and high portability.

[0062] In one embodiment of this application, skipping the business thread marked with annotations may include the following steps:

[0063] When the annotation of a business thread is marked as blocking, the business thread will be suspended.

[0064] When the annotation of the business thread is marked as interrupt, skip the business thread and return no response information about the business thread.

[0065] Specifically, for different types of business threads with lower importance, different types of annotation flags can be set according to actual needs, such as the blocking flag and interruption flag mentioned above. The blocking flag means that the corresponding business thread can be temporarily suspended and not processed until it can be processed later; the interruption flag means that the corresponding business thread can be skipped directly and no further processing is required.

[0066] Therefore, when it is determined that the current resource utilization rate within the system exceeds a preset threshold, for business threads with annotations, the annotation type can be determined first. If it is a blocking annotation, processing can be paused and the thread suspended directly; if it is an interrupt annotation, it can be skipped directly, and a no-response message for that business thread can be returned. The purpose of providing no-response feedback for business threads with interrupt annotations is to notify the front-end that the business thread has been processed. In other words, from the front-end's perspective, this business thread is one that has already been processed, while essentially it is a business thread that is skipped without further processing.

[0067] For business threads within the system that are relatively less important and require annotation identification, the specific type of annotation identification set does not affect the implementation of this technical solution. Technical personnel can set it according to the actual situation, and this application does not limit it in this regard.

[0068] In one embodiment of this application, the business processing method may further include the following steps:

[0069] When a wake-up command is received for a business thread that has a blocking flag set, the business thread is executed.

[0070] The business processing method provided in this application can perform a wake-up operation on business threads with a blocking flag set in the system, that is, it can perform a wake-up operation on suspended business threads in the system. Specifically, when a wake-up command for a business thread with a blocking flag set is received, the corresponding business thread can be woken up according to the wake-up command and executed, thereby realizing the processing of the suspended business thread. The method of obtaining the wake-up command is not unique; it can be initiated directly by the user through the front end, or it can automatically respond according to pre-set trigger conditions. This application does not limit this method.

[0071] In one embodiment of this application, the business processing method may further include the following steps:

[0072] Calculate the suspension duration of suspended business threads;

[0073] When the suspension time reaches the preset duration, respond to the wake-up command.

[0074] This application provides a method for obtaining a wake-up command. Specifically, for a suspended business thread, a suspension duration can be further set, i.e., the aforementioned preset duration. Then, during the suspension of the business thread, its suspension duration can be statistically analyzed in real time. If the suspension duration reaches the preset duration, a wake-up command can be automatically triggered, thereby obtaining the wake-up command. Thus, the corresponding business thread can be woken up and executed according to the wake-up command. The specific value of the preset duration does not affect the implementation of this technical solution, and different preset durations can be set for different suspended business threads. These can all be set by technicians according to actual conditions, and this application does not impose any limitations on this.

[0075] In one embodiment of this application, the business processing method may further include the following steps:

[0076] When the current resource utilization rate does not exceed the preset threshold, respond to the wake-up command.

[0077] This application provides another method for obtaining a wake-up command. Specifically, a load monitor can be used to collect the current resource utilization rate of the system in real time or at regular intervals. Once it is detected that the current resource utilization rate does not exceed a preset threshold, a wake-up command can be automatically received, thereby obtaining the wake-up command. Then, the corresponding business thread can be woken up and executed according to the wake-up command.

[0078] It should be noted that the two methods for obtaining the wake-up command mentioned above can coexist, allowing users to customize their selection according to their actual needs.

[0079] In one embodiment of this application, the above-mentioned method of obtaining the current resource utilization rate using a load monitor may include the following steps:

[0080] The load monitor collects and obtains the current resource utilization rate at preset time intervals.

[0081] This application provides a method for collecting current resource utilization based on a load monitor, which can be based on periodic collection at preset time intervals. Similarly, the specific values ​​of preset thresholds and preset durations mentioned above do not affect the implementation of this technical solution and can be set by technicians according to actual conditions; this application does not limit them.

[0082] Based on the above embodiments, this application provides another business processing method.

[0083] First, install a load monitor within the system and set annotations for each business thread according to actual needs. These annotations include `Blockable` and `Interrupted`. The `Blockable` annotation indicates that the business thread can be blocked when system resources are strained, and it supports setting `block_time` (block duration). Once blocked, the business thread cannot continue execution until it is awakened or a timeout occurs. The `Interrupted` annotation indicates that the business thread can be interrupted when system resources are strained. The load monitor is responsible for periodically monitoring CPU and memory usage, waking up blocked business threads when CPU and memory loads are low.

[0084] Furthermore, the implementation process of the business processing method may include:

[0085] (1) Start business processing, start the load monitor, and periodically collect the current CPU usage and current memory usage in the system through the load monitor;

[0086] (2) If the current CPU usage exceeds the corresponding threshold or the current memory usage exceeds the corresponding threshold, then execute (3); otherwise execute (7).

[0087] (3) Determine whether the current business thread has an annotation identifier set. If so, execute (4) or (5); otherwise, execute (6).

[0088] (4) If the annotation is marked as Blockable, the current business thread is blocked and a blocking time is set, waiting to be woken up or timed out; then switch to the next business thread and return (3);

[0089] (5) If the annotation is marked as Interruptable, skip the current business thread, throw an exception, and return a Serverbusy response; switch to the next business thread and return (3);

[0090] (6) Execute the current business thread;

[0091] (7) Execute each business thread in the system in sequence.

[0092] As can be seen, the business processing method provided in this application pre-marks low-importance business processes within the system with annotations and optimizes the business request processing mechanism. When executing business processes, the current system load is determined by assessing the current resource utilization rate. If the current resource utilization rate is high, it indicates a heavy system load. In this case, business threads marked with annotations can be skipped, and only those without annotations can be executed. That is, high-importance business threads are prioritized, while low-importance business threads are either deferred or not processed. Conversely, if the current resource utilization rate is low, it indicates a light system load, and all business threads within the system can be executed sequentially without distinguishing their importance. This achieves flexible allocation of system resources, effectively ensuring the normal operation of business processes. Furthermore, this implementation requires only minor modifications to existing system code, exhibiting low invasiveness and high portability.

[0093] This application provides a business processing apparatus.

[0094] Please refer to Figure 2 , Figure 2 This application provides a schematic diagram of the structure of a service processing apparatus, which may include:

[0095] Startup module 1 is used to start the load monitor when a business processing instruction is received;

[0096] Data acquisition module 2 is used to collect and obtain the current resource utilization rate using the load monitor;

[0097] The first execution module 3 is used to skip the business threads with annotations and execute the business threads without annotations if the current resource utilization rate exceeds a preset threshold.

[0098] The second execution module 4 is used to execute all business threads if the current resource utilization rate does not exceed the preset threshold.

[0099] As can be seen, the business processing apparatus provided in this application pre-marks low-importance business processes within the system with annotations and optimizes the business request processing mechanism. When executing business processes, it determines the current system load by judging the current resource utilization rate. If the current resource utilization rate is high, it indicates a high system load. In this case, business threads marked with annotations can be skipped, and only business threads without annotations can be executed. That is, high-importance business threads are prioritized, while low-importance business threads are either deferred or not processed. If the current resource utilization rate is low, it indicates a low system load, and all business threads within the system can be executed sequentially without distinguishing their importance. This achieves flexible allocation of system resources, effectively ensuring the normal operation of business processes. Furthermore, this implementation requires only minor modifications to existing system code, is minimally invasive, and has high portability.

[0100] In one embodiment of this application, the first execution module 3 may include:

[0101] The suspend unit is used to suspend a business thread when the annotation of the business thread is marked as blocking.

[0102] The feedback unit is used to skip the business thread and return no response information about the business thread when the annotation of the business thread is marked as interrupt.

[0103] In one embodiment of this application, the service processing apparatus may further include a wake-up module for executing the service thread when a wake-up instruction is received regarding the service thread that has a blocking flag set.

[0104] In one embodiment of this application, the service processing device may further include a first response module, used to count the suspension duration of the suspended service thread; when the suspension duration reaches a preset duration, it responds to a wake-up command.

[0105] In one embodiment of this application, the service processing device may further include a second response module, which is used to respond to a wake-up command when the current resource utilization rate does not exceed a preset threshold.

[0106] In one embodiment of this application, the acquisition module 2 described above can be specifically used to acquire the current resource utilization rate by using a load monitor at preset time intervals.

[0107] In one embodiment of this application, the current resource utilization rate may include the current CPU utilization rate and the current memory utilization rate.

[0108] For a description of the apparatus provided in the embodiments of this application, please refer to the above method embodiments; further details will not be repeated here.

[0109] This application provides an electronic device.

[0110] Please refer to Figure 3 , Figure 3 This application provides a schematic diagram of the structure of an electronic device, which may include:

[0111] Memory, used to store computer programs;

[0112] A processor is used to execute computer programs to implement the steps of any of the business processing methods described above.

[0113] like Figure 3 The diagram shows the structural composition of an electronic device, which may include a processor 10, a memory 11, a communication interface 12, and a communication bus 13. The processor 10, memory 11, and communication interface 12 all communicate with each other through the communication bus 13.

[0114] In this embodiment, the processor 10 may be a central processing unit (CPU), an application-specific integrated circuit, a digital signal processor, a field-programmable gate array, or other programmable logic devices.

[0115] The processor 10 can call programs stored in the memory 11. Specifically, the processor 10 can execute operations in the embodiments of the business processing method.

[0116] The memory 11 is used to store one or more programs. The programs may include program code, which includes computer operation instructions. In this embodiment, the memory 11 stores at least a program for implementing the following functions:

[0117] When a business processing instruction is received, the load monitor is activated;

[0118] Use a load monitor to collect and obtain the current resource utilization rate;

[0119] If the current resource utilization rate exceeds the preset threshold, skip the business threads with annotations and execute the business threads without annotations.

[0120] If the current resource utilization rate does not exceed the preset threshold, then all business threads will be executed.

[0121] In one possible implementation, the memory 11 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and applications required for at least one function; and the data storage area may store data created during use.

[0122] In addition, memory 11 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

[0123] Communication interface 12 can be an interface for the communication module, used to connect with other devices or systems.

[0124] Of course, it should be noted that, Figure 3 The structure shown does not constitute a limitation on the electronic device in the embodiments of this application. In practical applications, the electronic device may include more than Figure 3 More or fewer components as shown, or combinations of certain components.

[0125] This application provides a computer-readable storage medium.

[0126] The computer-readable storage medium provided in this application embodiment stores a computer program, which, when executed by a processor, can implement the steps of any of the above-described business processing methods.

[0127] The computer-readable storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0128] For a description of the computer-readable storage medium provided in the embodiments of this application, please refer to the above method embodiments; further details will not be repeated here.

[0129] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0130] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0131] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0132] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this application. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of this application.

Claims

1. A business processing method, characterized in that, include: When a business processing instruction is received, the load monitor is activated; The current resource utilization rate is obtained by using the load monitor. If the current resource utilization rate exceeds the preset threshold, the business threads with annotations are skipped, and the business threads without annotations are executed. If the current resource utilization rate does not exceed the preset threshold, then all business threads are executed; The step of skipping business threads with annotation identifiers includes: suspending the business thread when the annotation identifier of the business thread is a blocking identifier; and skipping the business thread and returning no response information about the business thread when the annotation identifier of the business thread is an interrupt identifier.

2. The business processing method according to claim 1, characterized in that, Also includes: When a wake-up command is received for a business thread that has the blocking flag set, the business thread is executed.

3. The business processing method according to claim 2, characterized in that, Also includes: Calculate the suspension duration of the suspended business threads; When the suspension time reaches the preset time, the wake-up command is responded to.

4. The business processing method according to claim 2, characterized in that, Also includes: When the current resource utilization rate does not exceed the preset threshold, the wake-up command is responded to.

5. The business processing method according to claim 1, characterized in that, The process of obtaining the current resource utilization rate using the load monitor includes: The load monitor is used to collect the current resource utilization rate at preset time intervals.

6. The business processing method according to claim 5, characterized in that, The current resource utilization rate includes the current CPU utilization rate and the current memory utilization rate.

7. A business processing apparatus, characterized in that, include: The startup module is used to start the load monitor when a business processing instruction is received; The data acquisition module is used to acquire the current resource utilization rate using the load monitor. The first execution module is used to skip the business threads with annotations set if the current resource utilization rate exceeds a preset threshold, and execute the business threads without the annotations set. The second execution module is used to execute all business threads if the current resource utilization rate does not exceed the preset threshold. Specifically, the first execution module is used to suspend the business thread when the annotation identifier of the business thread is a blocking identifier; and to skip the business thread and return no response information about the business thread when the annotation identifier of the business thread is an interrupt identifier.

8. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the business processing method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the business processing method as described in any one of claims 1 to 6.

Images