From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Better CPU for compiling with gcc
Date: Tue, 10 Nov 2015 13:41:46 -0600 [thread overview]
Message-ID: <5642487A.3040701@gmail.com> (raw)
In-Reply-To: <5642444D.9050205@gmail.com>
Alan McKinnon wrote:
> On 10/11/2015 21:07, Stanislav Nikolov wrote:
>>
>> 8GB of RAM are waaay more than I use daily (several firefox tabs, nvim = 2Gb max), I have a pretty fast SSD too. Even buying 8GB RAM and a brand new SSD, I have > $450 left. Can I buy a AMD CPU that will get the job done faster than 6700k and/or cheaper?
>>
>
> That changes things. It wasn't obvious you already had RAM & SSD & stuff.
>
> I'd first make sure I have a decent PSU - none of that crap puny
> el-cheapo $300 shit (search list archives for 1000s of posts about dodgy
> PSUs). Then split the difference between 8G RAM, a good CPU and an
> excellent motherboard. You will use that extra RAM, and a motherboard
> that ties all the bits together properly is much more cost-effective
> than raw CPU grunt alone.
>
If he needs a guide to at least increase the odds of getting a good P/S,
this may help.
http://www.jonnyguru.com/modules.php?name=NDReviews&op=Review_Cat&recatnum=13
I been reading their reviews for a few years. They are pretty tough.
To be honest, if I picked out one that rated 8 on their scale, that
would likely be a good P/S for me. You get into the 9's and it should
be a really good one. Short of lightening, it would be the last thing
I'd expect trouble from. They torture them pretty well. Should be the
worst a P/S should ever see, example, air conditioner goes out and its
really warm that day. Also, they take them apart so you can see what
is inside them, good brand of caps for example. Still, they include the
quality of the build and parts in their scoring. If a company skimps on
that, they deduct points.
Honestly tho, the P/S is a critical part. If it fails, it can wreak all
kinds of havoc. I've seen P/Ss go out and take a mobo, hard drive or
something else out with it. After all, pretty much everythign plugs
into power somehow.
Hope that helps.
Dale
:-) :-)
P. S. Makes me want to upgrade my CPU to a 8 core now. I need a hard
drive first tho. ;-)
next prev parent reply other threads:[~2015-11-10 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 17:47 [gentoo-user] Better CPU for compiling with gcc Stanislav Nikolov
2015-11-10 18:17 ` Mick
2015-11-10 18:37 ` Stanislav Nikolov
2015-11-10 18:55 ` Alan McKinnon
2015-11-10 19:07 ` Stanislav Nikolov
2015-11-10 19:21 ` Alec Ten Harmsel
2015-11-10 19:23 ` Alan McKinnon
2015-11-10 19:41 ` Dale [this message]
2015-11-11 19:05 ` Mick
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=5642487A.3040701@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