Stop
running
blocking
IO
actions
on
bounded
thread
pools.
Seriously. This is one of the hardest semantic issues to catch in code review. You can’t unit test it. It really only shows up in production, under load, as an ambiguous slow down.
-
-
Any examples of how this might be achieved in a web server? Does limiting the number of simultaneous connections count as a "higher level semaphore"?
-
Absolutely none of this is possible if you bound at the pool level.
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.