High concurrency and high response resolution in Java

A business with a low concurrency and a long task execution time should be differentiated:

If the business time is concentrated on I/O operations, that is I/O intensive tasks, because I/O operations do not occupy the CPU, so do not let all the CPU idle, you can increase the number of threads in the thread pool, so that the CPU processing more business.

If the business time is concentrated on the computation operations, that is, computationally intensive tasks, this is no way, and ①, the thread pool in the number of threads set less, reduce the thread context switch.

③ concurrency is high, business execution time is long, the key to solve this type of task is not in the thread pool but in the design of the overall architecture, to see if some of these business data can do cache is the first step, add the server is the second step, as to the thread pool settings, set reference ②.

Finally, the problem of long business execution may also need to be analyzed to see if the task can be split and decoupled using middleware.

High concurrency and high response resolution in Java