Method and terminal for dynamically dispatching thread pool

Abstract

The present invention provides a method and a terminal for dynamically scheduling thread pools. By presetting multiple thread pools, each thread pool has different numbers of threads, calculating the call frequency of a service interface, and dynamically scheduling the service interface according to the call frequency. A thread pool that matches the interface; it can dynamically schedule the thread pool corresponding to the business interface, avoid the problem of idleness and congestion of the thread pool caused by the mutual binding of the business interface and the thread pool, and optimize the thread pool resources, so as to realize reasonable and efficient scheduling of the thread pool .

Description

technical field [0001] The invention relates to the field of computer software, in particular to a method and a terminal for dynamically dispatching a thread pool. Background technique [0002] At present, a program project has many different business functions, and there may be various business interfaces according to different business functions, such as business interfaces with a large number of visits, business interfaces that consume a lot of time, or services with frequent delays Interface, when the interface response of the underlying service basic services such as database, network or IO is slow, it will occupy a large number of threads to process. If the request volume is large at this time, other interface requests will be blocked, delayed or unable to respond The problem. [0003] In view of the above problems, the existing technology usually allocates business interfaces into different thread pools, and each type of business interface can only run in the corresp...

AI Technical Summary

Problems solved by technology

[0002] At present, a program project has many different business functions, and there may be various business interfaces according to different business functions, such as business interfaces with a large number of visits, business interfaces that consume a lot of time, or services with frequent delays Interface, when the interface response of the underlying service basic services such as database, network or IO is slow, it will occupy a large number of threads to process. If the request volume is large at this time, other interface requests will be blocked, delayed or unable to respond The problem

[0003] In view of the above problems, the existing technology usually allocates business interfaces into different thread pools, and each type of business interface can only run in the corresponding thread pool. When the business interface thread of a certain thread pool is blocked, it will not occupy other thread pools. The resources of the thread pool avoid affecting the running of threads in other thread pools; however, the creation of these thread pools is usually programmed in advance, and a fixed thread pool is created as soon as the program project starts, that is, the business interface and its corresponding thread pool are fixed. Binding relationship, so for some business interfaces with unstable access, the corresponding thread pool will be sometimes idle and sometimes congested, so that the thread pool cannot be called reasonably efficiently

Images