On Oct 29, 7:43 pm, Lionel Bouton <[EMAIL PROTECTED]>
wrote:
> Maurício Linhares a écrit, le 10/29/2008 04:29 PM :
>
> > A slow SQL query woudn't freeze rails 2.2 as it freezes 2.1 now as the
> > MRI removes threads that are waiting for IO handles to be available
> > from the running list, so this should not be a big issue with the new
> > rails, but JRuby is a definitely better option today with the latest
> > rails.
>
> I'm not sure if the threading in Rails 2.2 brings any benefit for JRuby
> vs MRI. Last time I checked, even if JRuby used OS threads it used a
> global lock to make sure only one was running at one time (maybe to
> protect itself against race conditions in some Ruby code or parts of the
> implementation that isn't fully threadsafe yet). Did it change or are
That's just wrong (YARV/ruby 1.9 is a bit like that - you may have got
the idea from there). See the Charles Nutter's blog post (http://
blog.headius.com/2008/08/qa-what-thread-safe-rails-means.html ) which
Daniel already linked to.
Fred
> there some implementation details making it more thread friendly than MRI ?
>
> That said, JRuby could be better than MRI in many cases with Rails 2.1
> already, I'm just wondering if it recently got even better :-)
>
> Lionel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" 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/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
