Ok Robert, you are right.

So, if I have calls to native C libraries, my threads will be locked
there. So the only way to have concurrency there is with more than one
application?

On Oct 19, 2:35 pm, Robert Walker <rails-mailing-l...@andreas-s.net>
wrote:
> German wrote:
> > On the other hand, Clustering or pooling are solutions for Reliability
> > not for performance.
>
> I disagree. Clustering is primarily for scalability not reliability
> (although provides that as well). Performance actually provides little
> in terms of scalability. Increasing performance has limited usefulness
> in the ability of an application to scale. Clustering can provide
> theoretically unlimited scaleability.
>
> > Clustering does not give better performance, in
> > fact, most of the times gives you less performance one of the reasons
> > is the load balancer.
>
> While there may be some small overhead introduced by the load balancer
> it certainly does not offset the scalability advantages they provide. If
> you add just one additional instance of the application though a load
> balancer, it would have to slow the requests down by one half to loose
> overall scaleability. I'm sure that they do not introduce that level of
> overhead. The overhead is more likely negligible.
> --
> Posted viahttp://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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to