Rails can do either (config.thread_safe! turns on multithreading, and will
be the default in rails 4), but the deciding factor is what ruby
implementation you use: MRI doesn''t allow true concurrency in general
(specific cases like blocking on IO, waiting for a mysql query do permit
some concurrency). jruby doesn''t have this problem and rubinius has
also
done away with the global vm lock.
Fred
On Friday, October 5, 2012 6:23:36 AM UTC+1, Cary Cherng
wrote:>
> Can anyone tell me the current state of Rails and threading? Do you need a
> bunch of mongrel processes running on a single machine or is it possible to
> get away with just one that handles concurrent requests? I did a bunch of
> Google searches and couldn''t find a definitive answer on the
current
> request model used by Rails.
>
--
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit
https://groups.google.com/d/msg/rubyonrails-talk/-/AObU-V4nlKMJ.
For more options, visit https://groups.google.com/groups/opt_out.