The fibers are coroutines so when it yields it gives up control to whichever routine resumed it. Using a fiber pool is quicker and uses less memory than a thread pool. http://oldmoe.blogspot.com/2008/08/ruby-fibers-vs-ruby-threads.html
On Wed, Sep 10, 2008 at 10:03 PM, Sam Smoot <[EMAIL PROTECTED]> wrote: > > > > On Sep 10, 9:57 am, Sam Smoot <[EMAIL PROTECTED]> wrote: > > On Aug 30, 6:53 pm, oldmoe <[EMAIL PROTECTED]> wrote: > > > > > The thread will not block, only the fiber issuing the IO will. And you > > > can > > > have many fibers living in the same thread at a much lower cost than > > > spawning multiple threads in your application. > > > > I guess I fundamentally just don't get Fibers. If the fiber blocks, > > then it can't yield, so the thread is effectively blocked no? > > So as far as I can figure out, this is accurate. > > I think what I was forgetting was the GIL on 1.9. So I suppose it's > worth saying that I'm thinking more of something like JRuby's threads. > > -Sam > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
