First of all, Thanks frederick fr the fast response! I'll been tryint this, i found a BIG incrementation of the performance. On the other hand, i can't beleibe how this is a feature that I have to enable, and is not a default. What is the use of a web application, that can't handle 2 request at the same time? IMO that is useless. There are any concern about this?.. this feature is ready for production?.. or it is experimental.
I've read in some places that you must be sure that your code is thread safe, and that is obvious. Is there any other "problem" with that feature? Thanks On Oct 17, 1:32 pm, Frederick Cheung <[email protected]> wrote: > On Oct 17, 3:20 pm, German <[email protected]> wrote: > > > > > It is true that a single Rails App instance can't handle more than 1 > > request at the same time? > > It used to be true, but as of 2.2.2 you can turn on thread safe mode. > How much you benefit depends on what ruby interpreter you use what > your app does etc. > > Fred > > > > > I've been looking to the passenger solution for this, and the mongrel > > one, and others, but the solutions, are App pools, ans things like > > that, but nobody explain this in a right way. I need a direct answer > > to this question. > > > I know some workarounds, like clustering or pools, that's not what i > > want right now. > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
