Palanisamy Easwaran wrote:
> Hi,
>
> I am sorry for my ignorance,
> thanks for info, interesting to know about it.
> will it be useful for scalibility?
> -easwaran.P
>
Yes, that is what the original authors of this code built it for. I've heard
reports of apps that run better with multiple JVMs, even on a single server, when
there are multiple processors installed -- this is dependent on your JVM. It
also lets you distribute the servlet load over multiple seperate physical
servers.
The Apache JServ load balancing stuff will work best in the following types of
conditions:
* The work required by your servlet is pretty
compute bound, and/or the total memory load
is too big for one physical server.
* Most sessions last roughly the same amount of time
(so that the weighted assignment of new sessions does
not build up imbalances between servers).
* Most sessions make roughly the same kinds of demands
on the server (again, avoiding temporary imbalances).
* You want to be able to stop and start individual
JVMs without shutting down the whole application.
If workload is less evenly balanced, or if some sessions last a lot longer than
others, it is possible to build up temporary imbalances in workload between the
back end JVMs. Whether this matters or not is very application dependent.
The current implementation does not pay attention to the current load on any
server when it assigns new sessions to servers, and it never moves a session from
one server to another. High priced application servers are generally required to
do those tricks.
Craig
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
