Hi all,
sorry for the stress but it seems that it is a time to come back to the
discussion related to the load balancing for JVM (Tomcat).
Prehistory:
Recently we made benchmark and smoke tests of our product at the sun high
tech centre in Langen (Germany).
As the webserver apache2.2.4 has b
react on it , e.g. redirecting the
load.
Agreed, that this problem is not easy to solve and may be requires some
features from jvm side that are not implemented yet.
Regards,
Y.
--------
Yefym Dmukh
InterComponentWare AG
R
react on it , e.g. redirecting the
load.
Agreed, that this problem is not easy to solve and may be requires some
features from jvm side that are not implemented yet.
Regards,
Y.
--------
Yefym Dmukh
InterComponentWare AG
R
op-the-world
GC managed by lb, as keep it simple approach ?
Mladen Turk <[EMAIL PROTECTED]>
05.07.2007 13:19
Please respond to
"Tomcat Developers List"
To
Tomcat Developers List
cc
Subject
Re: Feature request /Discussion: JK loadbalancer improvements for high
load
Mladen wrote:
>This won't help much. The sticky session requests must be served
>by the same node (group of nodes if using domain clustering),
>and your requests will still be delayed by the JVM instance GC cycle
>(It has to happen sometime, and you cannot depend on request
>void intervals)
The ma
>Question, why would you need GC,heap or CPU stats from the Tomcat
>machine at all?
>in most cases, none of these stats can predict response times.
>The best way would be to simply record a history of response times, and
>then mod_jk can have algorithms (maybe even pluggable) on how to use
>thos
