On the other hand, Clustering or pooling are solutions for Reliability not for performance. Clustering does not give better performance, in fact, most of the times gives you less performance one of the reasons is the load balancer. It's true that every application has a limit of request to handle, all the servers have that limit, and there is where you need to do a pool or a cluster to "solve" the problem, but if my limit is "one request", i should think i have another problem..
On Oct 19, 12:24 pm, German <german.ot...@gmail.com> wrote: > Thanks, I have a passenger environment, with a pool of app's.. but > this schema is eating my server.. what if i have 10.000 rq per > second.. the solution is JRuby? > > On Oct 19, 11:29 am, Marnen Laibow-Koser <rails-mailing-l...@andreas- > > > > s.net> wrote: > > German wrote: > > > Is there a solution, for this issue?... i'm using postgres db. As far > > > as i understand what you say, every access to a native library, will > > > be locked and only one thread at a time will access. > > > Yes: use one of the pooled solutions like Passenger. I know you may > > think it silly, but at the moment, it's the best way if you're not using > > JRuby. > > > > On Oct 18, 8:06 pm, Frederick Cheung <frederick.che...@gmail.com> > > > Best, > > -- > > Marnen Laibow-Koserhttp://www.marnen.org > > mar...@marnen.org > > -- > > 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 -~----------~----~----~----~------~----~------~--~---
