From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ~amd64 compatibility with modern cpus -- REBOOT OK THIS A.M.
Date: Fri, 14 Dec 2012 15:19:53 -0600 [thread overview]
Message-ID: <50CB97F9.7080808@gmail.com> (raw)
In-Reply-To: <CA+czFiDzw9OpAbAi4oQH94oxXgJb-DFoQh9tqGJ81eU5RJpmXQ@mail.gmail.com>
Michael Mol wrote:
> On Fri, Dec 14, 2012 at 2:51 PM, <felix@crowfix.com> wrote:
>> I finally ran out of excuses to not reboot after a night powered off, and it did.
>>
>> It's all running normally now, but I think it's time for me to take the hint, grab a clue, and start researching a replacement.
> I think you'll find the power consumption of modern systems absolutely
> delightful compared to 8yo systems. I was amazed to see that
> server-grade xeon CPUs can be had for ~250USD, with a 77W TDP. 5-6
> years ago, my Phenom 9650 was a 120TDP part for almost that much when
> not on sale. (Yes, I know Intel and AMD don't calculate their thermal
> data quite the same way, but it seems comperable enough.)
>
> --
> :wq
>
>
I agree. My old rig, AMD 2500+ CPU with about 2Gbs of ram, a couple
hard drives and a FX-5200 video card pulled about 400 watts or so, not
counting the monitor. My new rig, AMD 4 core 3.2Ghz CPU, 16Gbs of ram,
4 hard drives and a GT-220 1Gb video card and it pulls less than 150
watts and just barely over 200 watts when compiling something and using
the drives a lot while doing it. That includes a LCD monitor too. My
old rig had a CRT monitor. Power hog big time which is why I didn't add
it to the power being pulled.
I did some math, my new rig is almost 8 times faster/powerful than my
old rig but pulls much less than half the power even when fully loaded.
I might add, I think the old rig was idle when I measured that.
I bet you could find some really old and cheap mobos, say a year or two
old but still new out of the box, and build a cheap system and have a
lot more powerful system that pulls less power from the wall. I saw a
Gigabyte mobo the other day on newegg for like $40.00. I'm sure the
model is a year or two old but still, its better than a 8 year old.
Also, memory is cheap for those too. Most likely the CPU would be too.
Sure is a weird problem tho. Sounds like something I would run into
myself. ;-)
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2012-12-14 21:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 16:18 [gentoo-user] ~amd64 compatibility with modern cpus felix
2012-12-14 16:28 ` Michael Mol
2012-12-14 16:33 ` felix
2012-12-14 16:47 ` Florian Philipp
2012-12-14 17:22 ` Volker Armin Hemmann
2012-12-14 17:35 ` felix
2012-12-14 18:16 ` Bruce Hill
2012-12-14 18:24 ` felix
2012-12-14 18:34 ` Bruce Hill
2012-12-14 18:43 ` felix
2012-12-14 18:48 ` Michael Mol
2012-12-14 18:52 ` Bruce Hill
2012-12-16 1:55 ` [gentoo-user] " Grant Edwards
2012-12-14 18:38 ` [gentoo-user] " Volker Armin Hemmann
2012-12-14 19:51 ` [gentoo-user] ~amd64 compatibility with modern cpus -- REBOOT OK THIS A.M felix
2012-12-14 20:00 ` Michael Mol
2012-12-14 21:19 ` Dale [this message]
2012-12-14 22:03 ` felix
2012-12-17 22:10 ` Robert Walker
2012-12-18 4:41 ` felix
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=50CB97F9.7080808@gmail.com \
--to=rdalek1967@gmail.com \
--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