Yes, 100 concurent requests is a sign you need lb - serving 1000 on one server is a false problem in most cases. I would rather have a server smartly reject requests and notify a lb rather then degrading all requests by accepting more than it can handle properly.
Try adding a database access or some realistic operation in the test servlet, and set the goal as 'no request above 1 second'. That would be a nice problem. Costin On 3/11/07, Henri Gomez <[EMAIL PROTECTED]> wrote:
2007/3/11, Costin Manolache <[EMAIL PROTECTED]>: > Great work - but I'm curious, wouldn't be better to explore the alternative > direction - i.e. detect when the server is too loaded and send a quick 502 ? > > Maybe with some extra logic - like serve existing sessions first, > provide some notifications that can be used by a load balancer ( or pager > :-) > to up more servers, or some notification to be used to disable some > expensive > functionality ? Something very welcome. Currently the HTTP/AJP couple is great for may of us but we still need better dynamic load switching. It's the same old question, how a load-balancer, ie mod_jk in lb, could know when to use a less loaded worker ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
