From: Matthew Marlowe <matt@deploylinux.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Somewhat OT. Building a rig. Want to get opinions before spending $$$
Date: Fri, 26 Nov 2010 22:14:05 -0800 [thread overview]
Message-ID: <201011262214.05864.matt@deploylinux.net> (raw)
In-Reply-To: <201011270429.14914.volkerarmin@googlemail.com>
Volker,
> Even my rig - hotter, doesn't reach 300W when I artificially torture the
> system. Normal 'max' load is in 200W range. An normal desktop? Under 100.
>
OK -- just to find out the truth I've attached a kill-a-watt to my current
workstation which is ~4yrs old w/ slow cpu and ancient video card but
has been upgraded w/ 7 SATA Drives:
Idle - ~285W
Light Use (emerge --sync) - ~310W
Kernel Compile w/ video app running and minor torture- ~340W
This is definitely much higher than 100-200W stated above.
Anyhow, given that the discussion was about a system lasting ~8yrs, which is
twice the current age of my system, I don't think it's unfeasible that future
upgrades (especially if video card related or if moving cpu from 2 core to 8
core) could get normal power util 20% higher to ~372W eventually.
If you conservatively state that PSU wattage should be 1.66 * normal util (so
that PSU is normally running at 60% of peak) then:
1.66 * 372 = 617
> So an 800W PSU is stupid in every regard. 650 is way to big. 450 is good
> enough. 400W might even be good enough.
>
OK, I'll agree that 800W is not looking very convincing. I must have bought
into the marketing there. Thanks for the correction.
However, 650W would seem to be optimal. For less stressful systems, 450 seems
OK short term, but I'm not sure whether it would be limiting for a chassis
expected to last 8+ yrs w/ whatever upgrades come down the line.
Matt
--
Matthew Marlowe / 858-400-7430 / DeployLinux Consulting, Inc
Professional Linux Hosting and Systems Administration Services
www.deploylinux.net * matt@deploylinux.net
'MattM' @ irc.freenode.net
next prev parent reply other threads:[~2010-11-27 6:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 21:29 [gentoo-user] Somewhat OT. Building a rig. Want to get opinions before spending $$$ Dale
2010-11-26 22:56 ` Matthew Marlowe
2010-11-27 3:29 ` Volker Armin Hemmann
2010-11-27 6:14 ` Matthew Marlowe [this message]
2010-11-27 6:59 ` Adam Carter
2010-11-27 7:48 ` Dale
2010-11-27 10:36 ` Volker Armin Hemmann
2010-11-27 11:27 ` Dale
2010-12-08 2:09 ` Dale
2010-12-08 18:19 ` Volker Armin Hemmann
2010-12-08 19:12 ` Dale
2010-12-08 19:47 ` Dale
2010-11-27 0:03 ` Jason Weisberger
2010-11-27 7:55 ` Dale
2010-11-27 3:23 ` Volker Armin Hemmann
2010-11-27 8:32 ` Dale
2010-11-28 16:57 ` [gentoo-user] " Dale
2010-11-28 17:13 ` Teemu Vartiainen
2010-11-28 17:26 ` Dale
2010-11-28 17:38 ` Volker Armin Hemmann
2010-11-28 19:07 ` Dale
2010-12-02 1:21 ` Dale
2010-12-05 22:48 ` masterprometheus
2010-12-05 23:51 ` Dale
2010-12-06 0:23 ` Mark Knecht
2010-12-06 1:21 ` Dale
2010-12-07 11:53 ` Dale
2010-12-07 11:59 ` Neil Bothwick
2010-12-07 12:17 ` Dale
2010-12-07 12:00 ` Hazen Valliant-Saunders
2010-12-07 12:26 ` Dale
2010-12-07 15:48 ` Volker Armin Hemmann
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=201011262214.05864.matt@deploylinux.net \
--to=matt@deploylinux.net \
--cc=gentoo-user@lists.gentoo.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