Hi Ben,
Thanks for your comments!
To answer your question, we can use SetThreadpoolThreadMinimum(pool, 1) and
SetThreadpoolThreadMaximum(pool, 1) to have a persistent single threaded
"windows event loop" that handles the IO and timer callbacks. This way, we
avoid the thread pool autoscaling
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
