On Aug 16, 10:36 pm, "s.ross" <[email protected]> wrote: > I think multi-threading is just another arrow in the quiver of the > good software designer. Having been down this road many times, I find > it difficult to characterize multi-threading as a "huge win" in the > context of Web applications.
I'll go a little bit controversial now: the fact that typical Rails deployments have to spin up multiple processes is totally mickey- mouse. What decade is this? With JRuby, just by avoiding the use of globally-accessible variables (globals, class variables) you can run an entire site with a single Rails instance in a single process. We've had reports from people running on 16-core boxes with JRuby in a single 100-200MB process, handling *thousands* of end-to-end requests per second. How many Mongrels or REE processes would you need to do that? At least 16 to make use of all the cores, and more if you don't want cores to sit idle half the time while blocking on IO. Multithreading in JRuby doesn't mean you need to write multi-threaded Rails apps; it means you get to take advantage of Rails thread-safe mode (2.2+) to shove as many requests as you possibly can through a single instance. No other Ruby implementation can do that. - Charlie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
