[erlang-questions] How to understand busyness of driver job queue?

Gleb Peregud gleber.p@REDACTED
Thu Mar 14 19:39:30 CET 2013

As far as I remember prim_inet does not use async IO threads. Please
correct me if I am wrong.

Sent from mobile, excuse me for brevity

On Wed, Mar 13, 2013 at 6:02 PM, Scott Lystig Fritchie
<fritchie@REDACTED> wrote:
> Michael Truog <mjtruog@REDACTED> wrote:
> mt> You may have thought that the async threads use a shared job queue,
> mt> but they don't... each thread has its own queue.  So, that means it
> mt> is easy to plug up the async thread pool, if you have long running
> mt> operations.  By increasing the pool size to a much larger value, you
> mt> are no longer blocking on a randomly overworked async thread.
> Small correction: you're less likely to block on an overworked async
> thread.  It's still possible to have two independent Erlang file
> handles/ports operating on different files that will always use the same
> async thread.
> -Scott
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list