Unbounded executor queues hide overload
An unbounded work queue can accept requests faster than workers process them, causing latency and memory growth. Bound the queue and define a rejection or backpressure policy.
"Unbounded executor queues hide overload" is a useful thing to know about with java / concurrency. Thanks for sharing it.
Fundamental
Awesome
- @sohmeh▲ 1
Appreciate the write-up on "Unbounded executor queues hide overload". Useful for anyone using java / concurrency.
Thorough
Overload stays invisible while an executor's queue has no limit, since submissions never fail. A bounded queue with a defined rejection or backpressure policy makes saturation show up early.
An unbounded queue keeps accepting tasks when workers fall behind, so latency and memory both grow. Set a capacity and choose what happens on rejection: block, drop, or fail the caller.
A
ThreadPoolExecutorwith a bounded queue rejects only after the queue is full and threads reachmaximumPoolSize, so the pool size matters too. Got a different fix? Post it in the comments.Clear note on java / concurrency. "Unbounded executor queues hide overload" is the kind of detail that is easy to overlook.
Appreciate the write-up on "Unbounded executor queues hide overload". Useful for anyone using java / concurrency.
Good to see "Unbounded executor queues hide overload" written down. Handy reference for anyone working with java / concurrency.
"Unbounded executor queues hide overload" is a useful thing to know about with java / concurrency. Thanks for sharing it.