From: "M. Fioretti" <m.fioretti@inwind.it>
To: linux-kernel@vger.kernel.org
Subject: Re: Unbloating the kernel, was: :mem=16MB laptop testing
Date: Fri, 24 Oct 2003 18:55:53 +0200 [thread overview]
Message-ID: <20031024165553.GB933@inwind.it> (raw)
In-Reply-To: <bnbi95$3qn$1@gatekeeper.tmr.com>
On Fri, Oct 24, 2003 15:59:33 at 03:59:33PM +0000, bill davidsen (davidsen@tmr.com) wrote:
> | > If we can ensure that Linux keeps working on these machines, it
> | > will be a good thing.
>
> Agreed, until you start to talk cluster. If you pay for electricity,
> newer machines use less per MHz. One of those $200 "Lindows" boxen
> from Wal-Mart starts to look good about the 2nd old Pentium!
May I ask you to elaborate on this? Less per MHz doesn't matter much
if the frequency is much higher, or it does? I mean, if you put, say,
a 133 MHz pentium and a 1 GB pentium to do the same thing with the
same SW (mail server, for example), the 1GB system may use less per
MHz (newer silicon, lower voltage, etc...) and its flip-flops toggle
for a smaller percentage of time, but its electricity bill will still
be the higher one, or not?
In general: has anybody ever done *this* kind of benchmarks? Comparing
electricity consumption among different systems doing just the same
task?
TIA,
Marco Fioretti
--
Marco Fioretti m.fioretti, at the server inwind.it
Red Hat for low memory http://www.rule-project.org/en/
A good man is intelligent, and a bad man is also an idiot. Moral and
intellectual characteristics go together - Jorge Luis Borges
next prev parent reply other threads:[~2003-10-24 16:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 11:44 Unbloating the kernel, was: :mem=16MB laptop testing Marco Fioretti
2003-10-14 12:02 ` William Lee Irwin III
2003-10-14 13:24 ` Rik van Riel
2003-10-14 14:30 ` jlnance
2003-10-14 14:54 ` Richard B. Johnson
2003-10-14 16:27 ` Maciej Zenczykowski
2003-10-14 17:33 ` John Bradford
2003-10-14 17:51 ` Richard B. Johnson
2003-10-15 12:43 ` Jan-Benedict Glaw
2003-10-15 13:06 ` William Lee Irwin III
2003-10-15 16:52 ` H. Peter Anvin
2003-10-15 13:08 ` Nick Piggin
2003-10-17 11:50 ` Jan-Benedict Glaw
2003-10-17 23:21 ` Nick Piggin
2003-10-14 18:35 ` tabris
2003-10-14 21:11 ` Roger Larsson
2003-10-15 11:45 ` Jan-Benedict Glaw
2003-10-15 13:06 ` William Lee Irwin III
2003-10-15 13:22 ` Jan-Benedict Glaw
2003-10-24 15:47 ` bill davidsen
2003-10-15 6:06 ` Sandy Harris
2003-10-24 15:59 ` bill davidsen
2003-10-24 16:55 ` M. Fioretti [this message]
2003-10-24 17:14 ` bill davidsen
2003-10-25 17:42 ` Geert Uytterhoeven
2003-10-28 9:12 ` Rob Landley
2003-10-14 21:43 ` Unbloating the kernel, action list M. Fioretti
2003-10-14 22:30 ` Martin J. Bligh
2003-10-14 22:56 ` cliff white
2003-10-15 12:48 ` Jan-Benedict Glaw
2003-10-15 13:10 ` William Lee Irwin III
2003-10-15 15:05 ` Jan-Benedict Glaw
2003-10-19 11:21 ` Adrian Bunk
2003-10-21 8:04 ` Jan-Benedict Glaw
2003-10-15 18:16 ` Gabriel Paubert
2003-10-16 5:19 ` Jan-Benedict Glaw
2003-10-16 8:16 ` Gabriel Paubert
2003-10-16 16:16 ` Jan-Benedict Glaw
2003-10-17 20:26 ` M. Fioretti
2003-10-17 20:10 ` M. Fioretti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031024165553.GB933@inwind.it \
--to=m.fioretti@inwind.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).