From: Willy Tarreau <w@1wt.eu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Peter Williams <pwil3058@bigpond.net.au>,
Esben Nielsen <nielsen.esben@googlemail.com>,
Ingo Molnar <mingo@elte.hu>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Con Kolivas <kernel@kolivas.org>, Nick Piggin <npiggin@suse.de>,
Mike Galbraith <efault@gmx.de>,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
caglar@pardus.org.tr, Gene Heskett <gene.heskett@gmail.com>,
Mark Lord <lkml@rtr.ca>, Zach Carter <linux@zachcarter.com>,
buddabrod <buddabrod@gmail.com>
Subject: Re: [patch] CFS scheduler, -v8
Date: Fri, 11 May 2007 21:37:51 +0200 [thread overview]
Message-ID: <20070511193751.GC20383@1wt.eu> (raw)
In-Reply-To: <20070511191824.GA7135@ucw.cz>
On Fri, May 11, 2007 at 07:18:25PM +0000, Pavel Machek wrote:
> Hi!
>
> > > Also notice that current cpus were not designed to work 300 years.
> > > When we have hw designed for 50 years+, we can start to worry.
> >
> > Indeed. CPU manufacturers don't seem to talk about it very much, and
> > searching for it with google on intel.com comes up with
> >
> > The failure rate and Mean Time Between Failure (MTBF) data is not
> > currently available on our website. You may contact Intel?
> > Customer Support for this information.
> >
> > which seems to be just a fancy way of saying "we don't actually want to
> > talk about it". Probably not because it's actually all that bad, but
> > simply because people don't think about it, and there's no reason a CPU
> > manufacturer would *want* people to think about it.
> >
> > But if you wondered why server CPU's usually run at a lower frequency,
> > it's because of MTBF issues. I think a desktop CPU is usually specced to
> > run for 5 years (and that's expecting that it's turned off or at least
> > idle much of the time), while a server CPU is expected to last longer and
> > be active a much bigger percentage of time.
> >
> > ("Active" == "heat" == "more damage due to atom migration etc". Which is
> > part of why you're not supposed to overclock stuff: it may well work well
> > for you, but for all you know it will cut your expected CPU life by 90%).
>
> Actually, when I talked with AMD, they told me that cpus should last
> 10 years *at their max specced temperature*... which is 95Celsius. So
> overclocking is not that evil, according to my info.
I tend to believe that. I've slowed down the FANs on my dual-athlon XP
to silent them, and I found the system to be (apparently) stable till
96 deg Celsius with FANs unplugged. So I regulated them in order to maintain
a temperature below 90 deg for a safety margin, and they seem to be as
happy as my ears. They've been like that for the last 3-4 years, I don't
remember.
On a related note, older technology is less sensible. My old VAX VLC4000
from 1991 which received a small heatsink in exchange for its noisy fans
is still doing well in an closed place. I'm more worried for the EPROMs
which store the boot code. Also, I think that the RS6000 processed at
half-micron which run the Mars rovers might run for hundreds of years
at 30 MHz.
> (That would mean way more than 10 years if you use your cpu
> 'normally'.)
>
> But I guess capacitors from cpu power supply will hate you running cpu
> at 95C...
even at 60, many of them die within a few years. Bu I think we're
"slightly" off-topic now...
> Pavel
Cheers
Willy
next prev parent reply other threads:[~2007-05-11 19:39 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 21:22 [patch] CFS scheduler, -v8 Ingo Molnar
2007-05-02 2:57 ` Ting Yang
2007-05-02 5:10 ` Willy Tarreau
2007-05-02 5:30 ` William Lee Irwin III
2007-05-02 10:05 ` Bill Huey
2007-05-02 10:27 ` Ingo Molnar
2007-05-02 17:36 ` Srivatsa Vaddagiri
2007-05-02 17:48 ` William Lee Irwin III
2007-05-02 18:15 ` Ingo Molnar
2007-05-02 18:56 ` William Lee Irwin III
2007-05-02 19:12 ` Ingo Molnar
2007-05-02 19:42 ` William Lee Irwin III
2007-05-03 2:48 ` Ting Yang
2007-05-03 3:18 ` Ting Yang
2007-05-03 10:19 ` Bill Huey
2007-05-02 23:41 ` Ting Yang
2007-05-02 18:42 ` Li, Tong N
2007-05-02 19:10 ` William Lee Irwin III
2007-05-03 3:07 ` Ting Yang
2007-05-03 8:50 ` Ingo Molnar
2007-05-03 14:26 ` Srivatsa Vaddagiri
2007-05-03 15:19 ` Ting Yang
2007-05-03 15:02 ` Ting Yang
2007-05-02 6:37 ` Mike Galbraith
2007-05-02 6:45 ` Ingo Molnar
2007-05-02 8:03 ` Gene Heskett
2007-05-02 8:12 ` Mike Galbraith
2007-05-02 8:48 ` Gene Heskett
2007-05-02 8:13 ` Ingo Molnar
2007-05-02 8:51 ` Gene Heskett
2007-05-02 7:59 ` Mike Galbraith
2007-05-02 8:11 ` Gene Heskett
2007-05-02 10:40 ` Ingo Molnar
2007-05-02 9:08 ` Balbir Singh
2007-05-02 10:05 ` Ingo Molnar
2007-05-02 10:59 ` Balbir Singh
2007-05-02 11:17 ` Ingo Molnar
2007-05-05 8:31 ` Esben Nielsen
2007-05-05 17:44 ` Linus Torvalds
2007-05-06 8:29 ` Ingo Molnar
2007-05-06 8:36 ` Willy Tarreau
2007-05-06 8:52 ` Ingo Molnar
2007-05-06 17:45 ` Linus Torvalds
2007-05-07 11:30 ` Esben Nielsen
2007-05-07 15:55 ` Ingo Molnar
2007-05-07 16:11 ` Linus Torvalds
2007-05-08 0:35 ` Peter Williams
2007-05-08 9:05 ` Esben Nielsen
2007-05-09 0:01 ` Peter Williams
2007-05-10 13:09 ` Pavel Machek
2007-05-11 16:50 ` Linus Torvalds
2007-05-11 19:18 ` Pavel Machek
2007-05-11 19:37 ` Willy Tarreau [this message]
2007-05-11 20:53 ` Kevin Bowling
2007-05-07 11:09 ` Esben Nielsen
2007-05-07 16:28 ` Linus Torvalds
2007-05-07 18:39 ` Johannes Stezenbach
2007-05-07 18:55 ` Linus Torvalds
2007-05-08 7:34 ` Esben Nielsen
2007-05-08 9:54 ` Johannes Stezenbach
2007-05-08 10:27 ` Esben Nielsen
2007-05-08 5:36 ` Matt Mackall
2007-05-02 12:58 ` Mark Lord
2007-05-02 12:58 ` Vegard Nossum
2007-05-02 16:41 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2007-05-03 8:20 Zoltan Boszormenyi
2007-05-03 13:02 ` Ingo Molnar
2007-05-03 13:29 ` Damien Wyart
2007-05-03 14:53 ` Srivatsa Vaddagiri
2007-05-03 15:53 ` William Lee Irwin III
2007-05-03 18:44 ` Li, Tong N
2007-05-03 19:52 ` William Lee Irwin III
2007-05-07 14:22 ` Srivatsa Vaddagiri
2007-05-07 20:54 ` Li, Tong N
2007-05-07 0:04 ` Bill Davidsen
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=20070511193751.GC20383@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=buddabrod@gmail.com \
--cc=caglar@pardus.org.tr \
--cc=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zachcarter.com \
--cc=lkml@rtr.ca \
--cc=mingo@elte.hu \
--cc=nielsen.esben@googlemail.com \
--cc=npiggin@suse.de \
--cc=pavel@ucw.cz \
--cc=pwil3058@bigpond.net.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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