On May 29, 2008, at 5:38 PM, andrzej wrote:
Hi,
module mod_proxy_balancer can make decision basing on volume of
traffic or number of requests. How, for example, this volume is
counted? Is it counted from the time server starts (hope not) or
maybe it is counted in 10 minutes period
Jim Jagielski wrote:
On May 29, 2008, at 5:38 PM, andrzej wrote:
Hi,
module mod_proxy_balancer can make decision basing on volume of
traffic or number of requests. How, for example, this volume is
counted? Is it counted from the time server starts (hope not) or
maybe it is counted in 10
Jim Jagielski pisze:
On May 29, 2008, at 5:38 PM, andrzej wrote:
Hi,
module mod_proxy_balancer can make decision basing on volume of
traffic or number of requests. How, for example, this volume is
counted? Is it counted from the time server starts (hope not) or maybe
it is counted in 10
Ryan Murray wrote:
IMHO LB is not at all a long-term action - if my LB worked like current
world stock market I'd return it to the vendor! Knowing that _over
time_ my
n clustered servers did the same amount of work is not nearly as
useful as
knowing that _right now_ my 2 servers are
On May 30, 2008, at 9:25 AM, Ryan Murray wrote:
In fact for many (if not most) monitoring and management situations,
moving
averages are more useful than infinitely historical data. If load
patterns
may change over time, it is often reasonable (or necessary) that
recent
traffic has
On May 30, 2008, at 9:10 AM, Jess Holle wrote:
Jim Jagielski wrote:
On May 29, 2008, at 5:38 PM, andrzej wrote:
Hi,
module mod_proxy_balancer can make decision basing on volume of
traffic or number of requests. How, for example, this volume is
counted? Is it counted from the time server
Hi,
module mod_proxy_balancer can make decision basing on volume of traffic
or number of requests. How, for example, this volume is counted? Is it
counted from the time server starts (hope not) or maybe it is counted in
10 minutes period (after 10 minutes values read and transfered are reset
