From: ralfconn <mentadent47@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Graphics configuration for a Ryzen 7 7700X chip and water cooling.
Date: Thu, 16 May 2024 22:27:39 +0200 [thread overview]
Message-ID: <bbbd7e5c-fd42-4751-a1fd-111ceaa74e4a@yahoo.com> (raw)
In-Reply-To: <c7453239-4c70-decf-1efe-99bd178ef65e@gmail.com>
Il 16/05/24 20:46, Dale ha scritto:
> Question. How are the compiles times between the old FX-8350 and the
> newer Ryzen 9? I currently have a FX-8350. Plan to build to a new
> Ryzen something, maybe 5 at first. Just curious what difference in
> speed you see.
I've not saved the merge times for the 8350 so I'll only give you the
Ryzen 9 times, maybe you can compare with yours:
# qlop -mav net-libs/webkit-gtk
net-libs/webkit-gtk-2.44.1-r410: 41′22″ average for 1 merge
net-libs/webkit-gtk-2.42.5-r410: 19′45″ average for 2 merges
net-libs/webkit-gtk-2.42.4-r600: 47′39″ average for 1 merge
net-libs/webkit-gtk-2.42.4-r410: 48′55″ average for 1 merge
net-libs/webkit-gtk-2.42.3-r410: 21′09″ average for 1 merge
# qlop -mav firefox
www-client/firefox-126.0: 31′35″ average for 1 merge
www-client/firefox-125.0.3: 13′29″ average for 1 merge
www-client/firefox-125.0.2: 12′42″ average for 1 merge
www-client/firefox-125.0.1: 30′18″ average for 1 merge
The 2x or more difference in merge times I believe are due to the fact
that sometimes I build the bigger packages on their own to avoid running
out of memory, other times I don't so the load gets split amongst
various compilations and time stretches. I think firefox with the 8350
was in the hours range, so I had switched to the -bin since long time.
I have 64Gb of RAM to account for the 12cpus/24threads. Even so I can
run out of memory if I try to build firefox+thunderbird+webkit-gtk at
the same time, so I often use the --exclude emerge option with these
behemoths.
I've also had a Ryzen 7 5700X/32Gb for a short time, then I passed it to
my son and got me the 9. These are the merge times for the webkit-gtk, I
switched to non-bin firefox only with the 9:
# qlop -mav net-libs/webkit-gtk
net-libs/webkit-gtk-2.40.5-r410: 26′52″ average for 1 merge
net-libs/webkit-gtk-2.40.4-r410: 25′16″ average for 1 merge
net-libs/webkit-gtk-2.40.3-r410: 59′46″ average for 1 merge
net-libs/webkit-gtk-2.40.2-r410: 32′47″ average for 2 merges
Not a huge difference compared to the 9, as foreseeable, after all it's
the exact same architecture with some more pepper.
If you go for the Ryzen remember that its instruction set is not
compatible with the Athlon's so if you built your 8350 system with e.g.
-march=native (as I did) you need to recompile @world with a less
restrictive -march before moving the disk to the Ryzen system otherwise
it won't even boot.
raf
next prev parent reply other threads:[~2024-05-16 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 14:23 [gentoo-user] Graphics configuration for a Ryzen 7 7700X chip and water cooling Alan Mackenzie
2024-05-15 15:14 ` Dale
2024-05-15 15:58 ` Peter Humphrey
2024-05-15 16:25 ` [gentoo-user] " Grant Edwards
2024-05-15 16:42 ` Matt Connell
2024-05-15 18:08 ` [gentoo-user] " Michael
2024-05-16 10:13 ` Frank Steinmetzger
2024-05-16 12:56 ` Michael
2024-05-16 15:30 ` ralfconn
2024-05-16 18:46 ` Dale
2024-05-16 20:27 ` ralfconn [this message]
2024-05-16 20:43 ` 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=bbbd7e5c-fd42-4751-a1fd-111ceaa74e4a@yahoo.com \
--to=mentadent47@yahoo.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