Cheers, Jon -- every little helps!
I'm gonna read for another hour, then let my brain rest.
I *think* I understand what's happening, now -- it's a continuation thing.
But I'm still stumped as to why people keep comparing them to threads so
readily. I mean, I see it, and that you can have them execute & pause &
continue, but why not just call them continuations? Why lightweight threads?
Which means, I guess, I *don't* really get it at all. :)
Thanks for the links!
   Doug.

On 13 June 2010 20:21, Jon R <[email protected]> wrote:

> If I understand them correctly, fibers are like ruby threads (so they
> still don't bypass the Global Interpreter Lock) but they aren't
> automatically schedule, you can manually tell them when to continue
> and pause etc so you can make the most of the cpu time. Positive I
> don't completly understand whats going on but check out this
> presentation and associated blog posts.
>
> http://www.slideshare.net/igrigorik/no-callbacks-no-threads-railsconf-2010
> http://www.igvita.com/2009/05/13/fibers-cooperative-scheduling-in-ruby/
> http://www.igvita.com/2010/06/07/rails-performance-needs-an-overhaul/
>
> May help, also this blog post
>
>
> http://www.mikeperham.com/2010/04/03/introducing-phat-an-asynchronous-rails-app/
>
> by mike perham has some interesting points about rails and event
> machine, may also be of use.
>
> On 13 June, 19:02, doug livesey <[email protected]> wrote:
> > But ... But ... But em-spec seems to be calling fibers like threads!
> > Augh!
> > Full circle!
> >
> > On 13 June 2010 18:41, doug livesey <[email protected]> wrote:
> >
> >
> >
> > > Yeah, genetic algorithms -- it was wanting to play with these that got
> me
> > > really into coding years ago, but then the more I coded professionally,
> the
> > > less time I spent on them. The problem with working obsessively is that
> > > there's too little time for fun!
> > > They're always in the back of my head, though, especially when I look
> at
> > > new languages or techniques.
> >
> > > On 13 June 2010 18:35, Ciaran <[email protected]> wrote:
> >
> > >> a
> > >> On Sun, Jun 13, 2010 at 6:29 PM, doug livesey <[email protected]>
> wrote:
> > >> > Well, after an afternoon's reading, I'm suspecting that I *have*
> rather
> > >> > missed the point, but am still waiting for all the pieces to settle
> in
> > >> my
> > >> > poor head.
> > >> > I was hoping they'd be something like Erlang's spawned processes,
> but
> > >> > they're not.
> > >> > They're still very cool continuations, though, and I think I've seen
> a
> > >> > really cool way I can implement a fair way to slice processor time
> up
> > >> for
> > >> > GAs & measure their efficiency with them. If I ever get to writing
> that
> > >> > particular project ... ;)
> > >> By GA's are we talking genetic algs or some other acronym here ?
> > >> -cj
> >
> > >> --
> > >> You received this message because you are subscribed to the Google
> Groups
> > >> "NWRUG" group.
> > >> To post to this group, send email to [email protected].
> > >> To unsubscribe from this group, send email to
> > >> [email protected]<nwrug-members%[email protected]>
> <nwrug-members%2bunsubscr...@goog legroups.com>
> > >> .
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/nwrug-members?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "NWRUG" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<nwrug-members%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/nwrug-members?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"NWRUG" 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/nwrug-members?hl=en.

Reply via email to