ThreadPoolExecutor - Core and maximum pool sizes

Question

When a new task is submitted in method execute(java.lang.Runnable),and fewer than corePoolSize threads are running, a new thread is created to handle the request, even if other worker threads are idle.

1) Why there is a need to create a new thread to handle the request if there are idle threads?

If there are more than corePoolSize but less than maximumPoolSize threads running, a new thread will be created only if the queue is full.

2) I don't understand the difference between corePoolSize and maximumPoolSize here. Secondly, how can a queue be full when threads are less than maximumPoolSize? Queue can only be full if threads are equal to or more than maximumPoolSize. Isn't it?

1. How does execute() know that your other worker threads are idle? Have you returned them back to the pool when you are done with them? — Robert Harvey, Jul 15 '13 at 17:23
2. It sounds like the ThreadPoolExecutor is trying to maintain a pool of usable threads larger than corePoolSize but smaller than maximumPoolSize. — Robert Harvey, Jul 15 '13 at 17:24

taynguyen · Answer 1 · 2017-02-28T08:50:53.140

28

Here are Sun’s rules for thread creation in simple terms:

If the number of threads is less than the corePoolSize, create a new Thread to run a new task.
If the number of threads is equal (or greater than) the corePoolSize, put the task into the queue.
If the queue is full, and the number of threads is less than the maxPoolSize, create a new thread to run tasks in.
If the queue is full, and the number of threads is greater than or equal to maxPoolSize, reject the task.

Full article

edited Feb 28 '17 at 08:50

answered Jan 27 '16 at 04:37

taynguyen

2,961
1
26
26

This is by far the most clear and concise description of what gets done. Thank you so much for this clear explanation. – Jack May 08 '19 at 19:35

score 8 · Answer 2 · answered Sep 02 '13 at 10:37

You can find the definition of the terms corepoolsize and maxpoolsize in the javadoc. http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html

The link above has the answer to your question. However, just to make it clear. The application will creating threads until it reaches the corePoolSize. It means that these number of threads should be sufficient to handle the inflow of tasks. After that the tasks will be queued. Once the queue is full the executor will start creating new threads. It is kind of balancing. What it essentially means is that the inflow of tasks is more than the processing capacity. So, Executor will start creating new threads again till it reaches Max number of threads. Again, a new threads will be created if and only if the queue is full.

Adelin · Answer 3 · 2014-01-29T22:34:39.403

Core and maximum pool sizes

A ThreadPoolExecutor will automatically adjust the pool size according to the bounds set by corePoolSize and maximumPoolSize .

When a new task is submitted in method execute(java.lang.Runnable), and fewer than corePoolSize threads are running, a new thread is created to handle the request, even if other worker threads are idle. If there are more than corePoolSize but less than maximumPoolSize threads running, a new thread will be created only if the queue is full.By setting corePoolSize and maximumPoolSize the same, you create a fixed-size thread pool.

By setting maximumPoolSize to an essentially unbounded value such as Integer.MAX_VALUE, you allow the pool to accommodate an arbitrary number of concurrent tasks. Most typically, core and maximum pool sizes are set only upon construction, but they may also be changed dynamically using setCorePoolSize(int) and setMaximumPoolSize(int). link

Please try to format your answer to improve readability. – harpun Jan 29 '14 at 22:18 — harpun, Jan 29 '14 at 22:18

ThreadPoolExecutor - Core and maximum pool sizes

3 Answers3

Linked