Thanks for all your reply
now i understand.
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
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
is a single thread(ruby green thread) created for everyone request?
I'm going to go out on a limb here since no others have responded, but
my understanding (at least in the current version of Rails) is no. I
don't believe than a thread is created at all. It is my understanding
that the Rails
Yes, mongrel_cluster is the way to go if you want to handle multiple
concurrent requests. I recommend nginx over Apache for load balancing
them, if you have the choice.
Threading is indeed hard, but it helps immensely with scaling
problems. That being said, Ruby threading is not very good at
On 8 Oct 2008, at 18:22, Michael Sofaer [EMAIL PROTECTED] wrote:
Yes, mongrel_cluster is the way to go if you want to handle multiple
concurrent requests. I recommend nginx over Apache for load balancing
them, if you have the choice.
Threading is indeed hard, but it helps immensely with
On 8 Oct 2008, at 17:32, Robert Walker [EMAIL PROTECTED]
s.net wrote:
is a single thread(ruby green thread) created for everyone request?
I'm going to go out on a limb here since no others have responded, but
my understanding (at least in the current version of Rails) is no. I
don't
Of course to see the most benefit you'll need a ruby implementation
with native threads, like jruby.
Or Ruby 1.9 YARV if I'm not mistaken?
Frederick Cheung wrote:
On 8 Oct 2008, at 18:22, Michael Sofaer [EMAIL PROTECTED] wrote:
...snip...
Fred
--
Posted via http://www.ruby-forum.com/.
On 8 Oct 2008, at 19:52, Robert Walker wrote:
Of course to see the most benefit you'll need a ruby implementation
with native threads, like jruby.
Or Ruby 1.9 YARV if I'm not mistaken?
IIRC ruby 1.9 is a bit special - threads are mapped to native threads,
but there's some giant mutex
7 matches
Mail list logo
