From: Robert Klemme <shortcutter@...>
Date: 2010-01-22T17:23:48+09:00
Subject: Re: Threads or Fibers - which should I use?

2010/1/22 Alpha Blue <jdezenzio@gmail.com>:
> Well, after doing a lot of research on this, I've come up with the
> following:
>
> Fibers would be faster and use less memory for blocking I/O.  Threads
> are necessary for blocking CPU.
>
> Because my app requires CPU blocking and I/O blocking I could
> incorporate both.  One of the fibers library I was looking over appears
> very solid:  (neverblock): http://github.com/oldmoe/neverblock
>
> I'm still looking over other solutions.

In your case I would start with threads because they are simpler to
use.  Fibers are really a means of cooperative multitasking and as
such have considerably higher programming overhead.  Also, either you
have one thread per Fiber or you will not be able to leverage the full
CPU power if you port your app to a Ruby version (say JRuby) which
supports native threads.

My 0.02EUR.

Kind regards

robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/