Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 20427 invoked from network); 11 Feb 2004 15:31:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Feb 2004 15:31:54 -0000 Received: (qmail 4379 invoked by uid 500); 11 Feb 2004 15:31:46 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 4342 invoked by uid 500); 11 Feb 2004 15:31:46 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 4286 invoked from network); 11 Feb 2004 15:31:45 -0000 Message-ID: <402A4AE2.8010506@algroup.co.uk> Date: Wed, 11 Feb 2004 15:31:46 +0000 From: Ben Laurie User-Agent: Mozilla Thunderbird 0.5b (Windows/20040204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bill Stoddard Cc: dev@apr.apache.org Subject: Re: routines for fetching load average? References: <4027F709.2090405@Golux.Com> <402A2480.1080705@Golux.Com> <402A354B.1050102@wstoddard.com> In-Reply-To: <402A354B.1050102@wstoddard.com> X-Enigmail-Version: 0.83.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Bill Stoddard wrote: > Rodent of Unusual Size wrote: > >> Rodent of Unusual Size wrote: >> >> >>> would anyone have any thoughts about the idea of adding an >>> api to obtain the system load average? i ask because i need >>> it for an httpd module i'm writing, and i've now got code >>> for linux, freebsd, os x, sunos, and t64u.. >> >> >> >> no thoughts, uh. > > > load average is nice but it seems rather specialized and it doesn't > really fit anywhere in apr[-util] that I see. load average is one > performance metric; I can see where it might be useful to have a common > interface for collecting all sorts of performance metrics. For example, > if Apache is being used as a load balancer, you could collect > performance state metrics from the servers being load balanced, feed > that info back to the apache load balancer (on an HTTP response header > field, via a special purpose HTTP POST request or out of band) and use > it in your load balancing/routing algorithms. Errr - mod_backhand? > I just don't see that this has a place in apr or apr-util. Maybe a new subproject, apr-perf? I don't follow your logic - APR is supposed to make the interface to the system portable. Load average is an interface to the system. Why does it need to "fit"? All it needs is support on enough platforms to be considered common and someone who wants to use it. Sounds like we have both. Are you seriously suggesting APR should only support things that are obvious extensions of what it already does? Cheers, Ben. -- http://www.apache-ssl.org/ben.html http://www.thebunker.net/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff