From: Francis Cianfrocca <garbagecat10@...>
Date: 2006-05-06T02:59:16+09:00
Subject: Re: Big Work Loads & Concurrency

------=_Part_2979_9902207.1146851946424
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Don, I thought about it a bit more. Your original question was how to
achieve concurrency. So there are evidently latencies in your system that
you'd like to capture, and my question is: how do these arise? If they come
from the network, then a solution like EventMachine is ideal. If they are
compute-bound, then you should also look at EventMachine, and you should no=
t
be looking at a threaded approach unless you're able to specify
multi-processor hardware. If the latencies are coming from elsewhere in you=
r
local system (such as disk i/o), then you should look at thread pools.

I hope that's helpful. Best of luck
-f

On 5/5/06, Don Stocks <amillionhitpoints@yahoo.com> wrote:
>
> Francis,
>
> I took a look at EventMachine. It looks very intersting.  But it seems
> that it's primary use is to abstract networking.  What are your thoughts
> on how this could be leveraged for use in the monitoring service I
> describe above (i.e. manage a large, dynamic queue of jobs and run them
> at specific intervals).
>
> Thanks! - Don
>
> Francis Cianfrocca wrote:
> > Depending on what you're trying to do, a single-threaded approach may
> > give
> > you more scalability and performance:
> > http://rubyforge.org/projects/eventmachine
>
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

------=_Part_2979_9902207.1146851946424--