Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 77552 invoked from network); 30 May 2008 13:59:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 May 2008 13:59:53 -0000 Received: (qmail 30286 invoked by uid 500); 30 May 2008 13:59:45 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 30270 invoked by uid 500); 30 May 2008 13:59:45 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 30259 invoked by uid 99); 30 May 2008 13:59:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2008 06:59:45 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.133.199.10] (HELO jimsys.jaguNET.com) (209.133.199.10) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2008 13:58:51 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by jimsys.jaguNET.com (Postfix) with ESMTP id B9BBD1AFC5A0 for ; Fri, 30 May 2008 09:59:12 -0400 (EDT) Message-Id: <452161BC-98BE-4069-8AAA-92DCF8402DFC@jaguNET.com> From: Jim Jagielski To: users@httpd.apache.org In-Reply-To: <4840004f.0405be0a.653d.ffffca29@mx.google.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Fri, 30 May 2008 09:59:12 -0400 References: <4840004f.0405be0a.653d.ffffca29@mx.google.com> X-Mailer: Apple Mail (2.924) X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] lbmethods in mod_proxy_balancer 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 significantly more weight than past traffic. This implies some knowledge of what has gone before and the timeframe associated with that. Not only that, but when you start bothering about short-term reactions, you can easily screw up the long-term results. Instant-by-instant LB is certainly a "viable" concept, but longer-termed averaging is a more sustainable solution, imo. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org