Important point in load balancing will be to collect CPU load (job load) from the remote. We often make the mistake to split requests between servers as if it cost the same CPU power (or cpu load) for each of them, but in Java / J2EE some requests could be more CPU/IO/DB consuming than others.
2006/6/19, Jim Jagielski <[EMAIL PROTECTED]>:
Ruediger Pluem wrote: > > On 06/19/2006 10:37 PM, Mladen Turk wrote: > > Henri Gomez wrote: > > > >> > >> For the load-balancing algorythm, do you plan to propose a bunch of > >> pre build algos and let users select the right one for their use or > >> allow externals modules ? We could see that like mod_jk / mod_proxy > >> modules like apache modules does for HTTP... > >> > > > > Something like that was suggested by Jim Jagielski more then > > a year ago. I think that the problem is that this would be > > a module of a module, and something like that was never done > > for httpd. Not even sure if its possible. > > Isn't this already the case right now? AFAIK the current lb algorithms are provider based. > So you can plug them in. From my understanding you can add further algorithms either to mod_proxy_balancer > or you can put them in an separate module that registers them separately. > That's right. I used the DAV/cache scenario when designing the provider impl in the balancer. -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "If you can dodge a wrench, you can dodge a ball."
