From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NAS box and switching from Phenom II X6 1090T to FX-6300
Date: Wed, 17 Apr 2024 15:24:50 -0500 [thread overview]
Message-ID: <16353c8d-a196-1683-94aa-178f88290efa@gmail.com> (raw)
In-Reply-To: <6c9fd3c52f88f72396f3d17c8e4a4eb7@gmail.com>
Meik Frischke wrote:
> Am 2024-04-17 12:33, schrieb Dale:
>> I found a benchmark website that compares the two. Link below. It
>> claims about 80% faster. In some ways, twice as fast. Sometimes those
>> bench tests don't reflect the real world to well. Most of them seem to
>> test gaming speeds which isn't of much use anyway for me. I'm more
>> about compiling and such. Just wondering how much speed difference this
>> would make. Maybe someone reading this did a similar upgrade or has
>> seen both in action. If so, post and share your thoughts.
>>
>
> Hi Dale,
>
> since Moore's Law isn't quite dead yet there is a significant
> performance uplift in newer processor generations, especially with the
> smaller 5nm process nodes of recent, after some years of stagnation at
> 14nm (your FX-8350 was manufactured at 32nm). With each process shrink
> (32nm -> 28nm -> 22 nm -> 14nm -> 10nm -> 7nm -> 5nm) new CPUs can
> deliver higher performance with the same power consumption or achieve
> similar performance levels with lower power consumption.
> Looking at the open-benchmarking default configuration kernel compile
> benchmark (pts/build-linux-kernel-1.15.0), the Ryzen 5 7600 (slower
> non-X) took ~101s to compile the kernel (based on 28 submitted
> results) while the FX-8350 took ~422s for the same task (based on 4
> submissions) [1]. Unlike gaming, compiling tends to scale quite well
> with core count and for the gentoo use-case the measured performance
> difference is in most cases similar for different packages. There are
> many influencing factors for benchmarking like running kernel version,
> activated options and mitigations so YMMV, but you can test it
> yourself: there are ebuilds for the phoronix-benchmark-suite in
> various overlays [2]. You can perform the benchmark with
> $(phoronix-test-suite benchmark pts/build-linux-kernel-1.15.0) with
> the "defconfig" test configuration option.
>
> Cheers,
> Meik
>
> [1]
> https://openbenchmarking.org/test/pts/build-linux-kernel&eval=9cdcd82c9c47af9df17263e4312f634338dbf476#metrics
> [2] https://gpo.zugaina.org/app-benchmarks/phoronix-test-suite
>
>
If one just compares the kernel compile time, about 4 times faster. I'm
not expecting the accuracy one needs to build a space ship. ;-) That's
a pretty good way to measure because with Gentoo, compiling a kernel is
a very common thing. As you said, it scales well. Compiling gcc would
be a good one to if they have default USE flags. Obviously if one
system has a lot of USE flags enabled and another is the bare minimum,
there will be a difference not related to CPU speed. Rich made a good
point too. Speed isn't just influenced by the CPU. Memory speed and
even the speed of accessing data drive, spinning rust, SSD or whatever,
also affects a system.
When I get this new rig built and you see me post about it, remind me
and I'll install that benchmark test and send in the results. I like
doing things like that because it helps others too. I just wish there
was a centralized place for them all. Right now, there are likely
dozens of them and each with their own method.
Thanks for that info. I'm making progress and planning a way to
purchase all this. It's still not cheap but cheaper than it was before
I found out I could get a cheaper CPU and upgrade later.
Dale
:-) :-)
next prev parent reply other threads:[~2024-04-17 20:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 7:58 [gentoo-user] NAS box and switching from Phenom II X6 1090T to FX-6300 Dale
2024-04-13 8:35 ` Michael
2024-04-13 11:12 ` Dale
2024-04-13 11:38 ` Michael
2024-04-13 12:11 ` Dale
2024-04-13 12:30 ` Rich Freeman
2024-04-13 13:23 ` Dale
2024-04-13 16:26 ` Wols Lists
2024-04-13 16:59 ` Dale
2024-04-15 10:50 ` Frank Steinmetzger
2024-04-15 13:04 ` Dale
2024-04-15 13:31 ` Frank Steinmetzger
2024-04-15 16:13 ` Dale
2024-04-17 10:33 ` Dale
2024-04-17 12:10 ` Rich Freeman
2024-04-17 13:33 ` Dale
2024-04-17 17:18 ` Rich Freeman
2024-04-17 20:15 ` Frank Steinmetzger
2024-04-17 20:35 ` [gentoo-user] " Grant Edwards
2024-04-17 22:13 ` [gentoo-user] " Dale
2024-04-18 11:42 ` Michael
2024-04-18 12:26 ` Dale
2024-04-18 12:35 ` Frank Steinmetzger
2024-04-18 15:09 ` Dale
2024-04-18 13:36 ` Mike Civil
2024-04-17 21:39 ` Dale
2024-04-17 17:37 ` Meik Frischke
2024-04-17 20:24 ` Dale [this message]
2024-04-13 11:45 ` Rich Freeman
2024-04-13 12:20 ` Dale
2024-04-13 12:34 ` Rich Freeman
2024-04-13 13:35 ` Dale
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=16353c8d-a196-1683-94aa-178f88290efa@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