utoscaling beyond the number of CPUs, so that the
libprocess worker threads don't get starved. We won't be using the work queue
aspect of the thread pool.
Thanks,
Akash
-Original Message-
From: Benjamin Mahler
Sent: Thursday, April 12, 2018 6:30 PM
To: dev
Subject: Re: Propo
Thanks for writing this up and exploring the different options Akash!
I left some comments in the doc. It seems to me the windows thread pool API
is a mix of "event" processing (timers, i/o), as well a work queue. Since
libprocess already provides a work queue via `Process`es, there's some
overlap
Hi all,
A few weeks ago, we found serious issues with the current asynchronous IO
implementation on Windows. The two eventing libraries in Mesos (libevent and
libev) use `select` on Windows, which is socket-only on Windows. In fact, both
of these libraries typedef their socket type as SOCKET,
