Yes, I mean blocking io.
On Jul 21, 2016 11:35 PM, "Arindam Mukherjee"
wrote:
> You mean doing blocking I/O in the worker threads? Or using EventMachine
> somehow? Sorry for not understanding.
>
> On Friday, 22 July 2016 11:51:48 UTC+5:30, raggi wrote:
>>
>> Why not just use Ruby's Queue class,
You mean doing blocking I/O in the worker threads? Or using EventMachine
somehow? Sorry for not understanding.
On Friday, 22 July 2016 11:51:48 UTC+5:30, raggi wrote:
>
> Why not just use Ruby's Queue class, and do io in your worker threads,
> sizing your pool appropriately to fill cpu while wai
Why not just use Ruby's Queue class, and do io in your worker threads,
sizing your pool appropriately to fill cpu while waiting on io?
On Jul 21, 2016 11:10 PM, "Arindam Mukherjee"
wrote:
> I am trying to build a task broker using EventMachine, thread pools and a
> fibers. I wanted to validate t
I am trying to build a task broker using EventMachine, thread pools and a
fibers. I wanted to validate the approach and ask questions about some
challenges I am facing.
The task broker runs a thread-pool (perhaps not EM.defer) to which
individual tasks are assigned.
The tasks are I/O bound, but
