Oracle's old Application Server product did this. There were many exciting
tuning parameters for how many threads per JVM, how many objects, etc.. At
the time the issue was really the poor scalability of the threads within the
JVMs. It seems thos issues are past, so there is much less need for the
multiple JVM approach.
Cheers
-----Original Message-----
From: Lauren Commons [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 2:13 PM
To: [EMAIL PROTECTED]
Subject: Re: Entity beans, clistering and scalability
--- Jeff Schnitzer <[EMAIL PROTECTED]> wrote:
> why on earth would
> starting multiple
> VMs on the same box increase scalability?
This doesn't make a whole lot of sense to me either,
but on a project a couple years ago, using Weblogic
(called Tengah then? sigh... those where the good old
days) the client was trying to improve performance,
and Weblogic said the same thing: run as many
instances in as many JVMs as you can on the server.
Unfortunately the app wasn't really designed with that
in mind, so...
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
