I have had a need  for this functionality in one application or other for a while now and have been researching various means of acheiving it without actually coding.

mod_backhand ( www.backhand.org) which seems to be an abandoned project was very promising a few years back.
I think, section 3.3 of http://www.backhand.org/ApacheCon2001/US/backhand_course_notes.pdf was some attempt in the past in this direction.

Just wanted to put in this casual note.

Thanks for keeping up the good work folks - appreciate it
Cheenu

On 6/20/06, Mladen Turk <[EMAIL PROTECTED]> wrote:
Henri Gomez wrote:
> 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.
>

Well, I'm not sure that having the CPU load would mean something.
For example you might have P3/1GHz and P66/100GHz with the
same load (close to 80%), and that info in that case would be
actually misleading. It might help only if your hardware topology
is exactly the same for all backend servers.

The bussines method OTOH will favor the 100GHz box over 1GHz one,
thus giving more sense. Even with the same hardware topology,
it is presumable that the shorter reply timeout would mean less
CPU cycles used.

Regards,
Mladen.

Reply via email to