From owner-freebsd-arch@FreeBSD.ORG Tue Mar 18 19:52:04 2008 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92327106564A; Tue, 18 Mar 2008 19:52:04 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 693D58FC1A; Tue, 18 Mar 2008 19:52:04 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.64.3]) by phk.freebsd.dk (Postfix) with ESMTP id 96FFB17105; Tue, 18 Mar 2008 19:52:02 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m2IJq2WK001279; Tue, 18 Mar 2008 19:52:02 GMT (envelope-from phk@critter.freebsd.dk) To: Robert Watson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 18 Mar 2008 18:26:11 GMT." <20080318182358.F34016@fledge.watson.org> Date: Tue, 18 Mar 2008 19:52:02 +0000 Message-ID: <1278.1205869922@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: arch@FreeBSD.org, Kris Kennaway Subject: Re: Power-Mgt (Was: Re: cvs commit: src/sys/i386/cpufreq est.c ) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Mar 2008 19:52:04 -0000 In message <20080318182358.F34016@fledge.watson.org>, Robert Watson writes: >I know we've talked about this, but I'll mention it for the benefits of the >mailing list: one of the things that makes performance an "easy" target is >that there are easy-to-gather metrics. [...] Are >there any decent documents describing how to do power use measurement, and are >there any (relatively) accessible tools for doing it with? I think performance and power-performance is pretty similar in this: you can easily collect some pretty crude performance indications and it takes a determined effort to get hard numbers. When we talk about macroscopic efforts, turning of hardware we don't use, spinning down disks, common sense says that power is saved and we can leave it at that. When we talk about optimizing scheduling to keep chips powered off as much as possible, it will more than the average ampmeter to inform about the optimal algorithms. I have not tried to find out how exact the power measurements ACPI offers on laptops are, I know some of the chips used but have never double-checked the result. Obviously, if you have access to a decent bench supply, you can run your laptop off that (take the battery out so charging does not affect the results), but few off them allow you to measure power (ie: Watts) without hooking up GPIB and accumulating a lot of current measurements by hand. Summary: There isn't anything as handy as time(1), but it isn't rocket science either. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.