If you have multiple CPU cores then of course you still need to be running multiple merb processes, since ruby threads are not native (although they can be started with one command - merb -c #processes).
It would be interesting to know if anyone has any metrics for the performance of a single multithreaded merb process relative to multiple single threaded merb processes on a single processor box. Martyn On Wed, Oct 22, 2008 at 10:25 AM, Matthijs Langenberg <[EMAIL PROTECTED]> wrote: > > One process to rule them all. Though I don't understand why people are > still starting about three processes on the same machine. > > On Wed, Oct 22, 2008 at 10:43 AM, weepy <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> Does a threadsafe merb/rails mean that there's much less reason to run >> clusters of webservers? I.e. previously to handle N simultaneous >> requests meant that you should run N servers. >> >> weepy ;..( >> > >> > > > > -- Martyn Loughran Creating fresh, flexible and fast-growing web applications is our passion. http://www.new-bamboo.co.uk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
