java:threadpoolexecutor
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| java:threadpoolexecutor [2025/02/22 00:02] – carl | java:threadpoolexecutor [2025/02/22 18:40] (current) – [ScheduledThreadPoolExecutor] carl | ||
|---|---|---|---|
| Line 34: | Line 34: | ||
| + | ====== ScheduledThreadPoolExecutor ====== | ||
| + | This class is similar to ThreadPoolExecutor, | ||
| + | === Living without a Queue === | ||
| + | |||
| + | A consequence of not being able to bound the queue is that the thread count is more important: | ||
| + | |||
| + | * You cannot have a cached ScheduledThreadPoolExecutor. | ||
| + | * As mentioned in the javadocs, a core pool size of 0 is practically useless, since no threads will be alive to process the task. | ||
| + | * If all the threads in the ScheduledThreadPoolExecutor are busy (e.g. blocking), no new tasks can be executed. | ||
java/threadpoolexecutor.1740211349.txt.gz · Last modified: by carl
