I agree - java server processes can get HUGE. I work with weblogic clusters and we constantly have to change the thread pools and stack size on the threads because they can get wayyy out of hand.
Has anyone successfully created mongrel clusters spanning two or more physical servers? Just curious. Ryan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Verkhovsky Sent: Thursday, March 08, 2007 10:52 AM To: mongrel-users@rubyforge.org Subject: Re: [Mongrel] Memory leaks in my site On 3/8/07, Zed A. Shaw <[EMAIL PROTECTED]> wrote: C'mon, Java processes typically hit the 600M or even 2G ranges and that's just common place. Java runtime is a bloat. But its processes are natively multi-threaded and can serve multiple apps from the same server. So, one Java process should probably be compared with about 5-10 Rails processes in terms of RAM footprint. It's still a bloat. Even better, why are people complaining about the memory footprint of RAILS on the MONGREL mailing list? Not guilty. In this thread, I am complaining about Mongrel's memory footprint, not "Hello, World"'s. :) Besides, I'm not even complaining, just trying to understand the ins and outs of this stack, and what can or cannot be squeezed out of it. By the way, I hope load balancing solutions are not off-topic? :) Alex
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
