mimimum hardware requirements: primary purpose: compiling

Message

jindam · Post by **jindam** » Sun Jun 25, 2023 5:45 pm

* read few forum posts, they were not very specific
[ perhaps i am wrong ]
* i want to compile much everything required
for every major and minor dot release of gcc
[ long term goal ]
* software: libreoffice-writer , firefox, emacs,
xfce, inkscape, openjdk, claws-mail, tor browser, qt
* i will compile [ from latest git build ]
** libreoffice-writer atleast twice a week
** inkscape - daily
** firefox - on need basis
** kernel - once a week
* eventually replace gtk packages with
qt variants
* please suggest mimimum hardware requirements
for the above needs

regards,
jindam

p.s. i was asking same on irc, however
network was against my intentions

logrusx · Post by **logrusx** » Sun Jun 25, 2023 6:53 pm

Hello and welcome to the forums!

The most important rule: 2GB of RAM per thread. The rest depends on your budget and taste.

Best Regards,
Georgi

flysideways · Post by **flysideways** » Sun Jun 25, 2023 7:31 pm

There is plenty of room if you have 16gb ram min or 4gb per thread. 128gb of hard drive should suffice if all you do is build and keep it clean, but 500gb drives don't cost much these days.

It becomes a question of how fast do you want to go. As an example my Pi 4 w/8gb ram took 16 hours to compile a version of gcc 12, an M1 Max macbook took almost 24 minutes for the same, and a 12 core/24 thread ryzen box also took about 24 minutes.

Post by **NeddySeagoon** » Sun Jun 25, 2023 7:41 pm

jindam,

Welcome to the forums.

* i will compile [ from latest git build ]

That's scary. the tip of git trees often do not build. The only reason to do that is if you are a developer working the the package.

jindam · Post by **jindam** » Sun Jun 25, 2023 11:18 pm

NeddySeagoon wrote:jindam,

Welcome to the forums.

* i will compile [ from latest git build ]
That's scary. the tip of git trees often do not build. The only reason to do that is if you are a developer working the the package.

If they fail, i will search online. If search didnt yield results,
Or couldnt make sense, simply ask in irc whether it is worth
to create an issue. Just like asking here before plunging....
Arent the daily builds are compiled from tip of the git?

jindam · Post by **jindam** » Sun Jun 25, 2023 11:28 pm

flysideways wrote:It becomes a question of how fast do you want to go.

fast enough, ex: libreoffie-writer compile finish within 4 hours.
within or nearly 4 hours max expecting to compile finish.

flysideways wrote:As an example my Pi 4 w/8gb ram took 16 hours to compile a version of gcc 12, an M1 Max macbook took almost 24 minutes for the same, and a 12 core/24 thread ryzen box also took about 24 minutes.

If budget permits, will go for atleast 24 core/48 thread
or else 12 core/24 thread.

figueroa · Post by **figueroa** » Mon Jun 26, 2023 3:29 am

It's clear you aren't asking about minimum requirements. Maybe you explain why you want to burn so much energy?

The full LibreOffice package compiles and installs in about 2 hours in my setup (see below sig).

jindam · Post by **jindam** » Mon Jun 26, 2023 5:18 am

figueroa wrote:Maybe you explain why you want to burn so much energy?

atleast 24 core/48 thread may be you are
intrigued....
to compile other packages on daily basis.....
investing in right configuration: future proof
but, its another story only if i become some
sort of expert to compile everything... like lfs, blfs, alfs...
everything must be according to my thinking...
may be after 3 years?

figueroa wrote:The full LibreOffice package compiles and installs in about 2 hours in my setup (see below sig).

wow!!!!!

rfx · Post by **rfx** » Mon Jun 26, 2023 5:34 am

figueroa wrote:It's clear you aren't asking about minimum requirements. Maybe you explain why you want to burn so much energy?

The full LibreOffice package compiles and installs in about 2 hours in my setup (see below sig).

On my Intel Celeron n5105 (4x 2,8ghz) with 16gb ddr4 and a 12gb tmpfs libreoffice took 207 minutes to compile

@jindam i don´t understand why you open a threat, wanting to know the minimum requirements to compile something and then you buy a 48threat desktop system

You shouldn´t have any problems with minimum requirements

logrusx · Post by **logrusx** » Mon Jun 26, 2023 7:17 am

jindam wrote:
figueroa wrote:Maybe you explain why you want to burn so much energy?
atleast 24 core/48 thread may be you are
intrigued....
to compile other packages on daily basis.....
investing in right configuration: future proof
but, its another story only if i become some
sort of expert to compile everything... like lfs, blfs, alfs...
everything must be according to my thinking...
may be after 3 years?

figueroa wrote:The full LibreOffice package compiles and installs in about 2 hours in my setup (see below sig).
wow!!!!!

I didn't understand much. Get yourself clear on what it is that you want to achieve. You won't become an expert just by compiling.

Best Regards,
Georgi

Post by **NeddySeagoon** » Mon Jun 26, 2023 10:26 am

jindam,

libreoffice,

Code: Select all

     Thu May 25 20:57:50 2023 >>> app-office/libreoffice-7.5.3.2
       merge time: 21 minutes and 46 seconds.

     Tue Jun 13 23:05:40 2023 >>> app-office/libreoffice-7.5.4.2
       merge time: 33 minutes and 26 seconds.

     Sat Jun 17 19:49:20 2023 >>> app-office/libreoffice-7.5.4.2
       merge time: 21 minutes and 49 seconds.

www-client/firefox

Code: Select all

     Sun May 21 21:15:18 2023 >>> www-client/firefox-113.0.1
       merge time: 30 minutes and 36 seconds.

     Thu May 25 19:07:00 2023 >>> www-client/firefox-113.0.2
       merge time: 19 minutes and 46 seconds.

     Tue Jun 13 22:24:55 2023 >>> www-client/firefox-114.0
       merge time: 35 minutes and 15 seconds.

That's with Bucket List PC

Some guidelines.

For each CPU thread, allow 2G RAM. That's for gcc today. It will get worse. Add some for the system too.
Build in RAM too, that's /var/tmp/portage in tmpfs. That's yet more RAM.
Very few individual packages can keep 30 make jobs in flight concurrently. I tried really hard on a 96 core Cavium Thunder X2 system, There are a few exceptions.
Allow for growth over the life of the system, either by provisioning for it now, or by adding parts later.

With the above constraints, pick your price point.

Even then the configure and link steps are single threaded.

stefan11111 · Post by **stefan11111** » Mon Jun 26, 2023 11:01 am

NeddySeagoon wrote: That's with Bucket List PC

More like monster rig.
Just the cpu is 50 $ short of what I got my pc for 4 years ago.

Code: Select all

2023-06-19T15:26:43 >>> www-client/librewolf: 2:37:39
2023-06-20T03:48:29 >>> www-client/librewolf: 2:33:40
2023-06-20T20:49:55 >>> www-client/librewolf: 2:09:25
2023-06-21T03:57:49 >>> www-client/librewolf: 2:03:14
2023-06-21T21:44:12 >>> www-client/librewolf: 2:35:39

nikolis · Post by **nikolis** » Mon Jun 26, 2023 10:12 pm

NeddySeagoon wrote: www-client/firefox

Code: Select all

     Sun May 21 21:15:18 2023 >>> www-client/firefox-113.0.1
       merge time: 30 minutes and 36 seconds.

     Thu May 25 19:07:00 2023 >>> www-client/firefox-113.0.2
       merge time: 19 minutes and 46 seconds.

     Tue Jun 13 22:24:55 2023 >>> www-client/firefox-114.0
       merge time: 35 minutes and 15 seconds.

this compile time seems to me too long for your 5950X, unless you are doing other tasks at the same time. I don't remember how long it takes my ryzen 7700X to finish firefox because I put it to work at night when I go to sleep. I'll look into it tomorrow and let you know.

jindam wrote: please suggest mimimum hardware requirements
for the above needs

regards,
jindam

If you are a developer, I would suggest a ryzen 7950X + 128gb ddr5 + motherboard around €1500.
If you are a home user, I think the best vfm is a ryzen 3600 65W about €70 with 2x16gb €50 ram ddr4 + motherboard 130€ b550 total €250.

figueroa · Post by **figueroa** » Mon Jun 26, 2023 11:17 pm

nikolis -- Use the command:

Code: Select all

qlop firefox

to see emerge time history on your machine. qlop is part of app-portage/portage-utils.

logrusx · Post by **logrusx** » Tue Jun 27, 2023 5:04 am

NeddySeagoon wrote:jindam,

libreoffice,
Code: Select all
     Thu May 25 20:57:50 2023 >>> app-office/libreoffice-7.5.3.2
       merge time: 21 minutes and 46 seconds.

     Tue Jun 13 23:05:40 2023 >>> app-office/libreoffice-7.5.4.2
       merge time: 33 minutes and 26 seconds.

     Sat Jun 17 19:49:20 2023 >>> app-office/libreoffice-7.5.4.2
       merge time: 21 minutes and 49 seconds.
www-client/firefox
Code: Select all
     Sun May 21 21:15:18 2023 >>> www-client/firefox-113.0.1
       merge time: 30 minutes and 36 seconds.

     Thu May 25 19:07:00 2023 >>> www-client/firefox-113.0.2
       merge time: 19 minutes and 46 seconds.

     Tue Jun 13 22:24:55 2023 >>> www-client/firefox-114.0
       merge time: 35 minutes and 15 seconds.
That's with Bucket List PC

Some guidelines.

For each CPU thread, allow 2G RAM. That's for gcc today. It will get worse. Add some for the system too.
Build in RAM too, that's /var/tmp/portage in tmpfs. That's yet more RAM.
Very few individual packages can keep 30 make jobs in flight concurrently. I tried really hard on a 96 core Cavium Thunder X2 system, There are a few exceptions.
Allow for growth over the life of the system, either by provisioning for it now, or by adding parts later.

With the above constraints, pick your price point.

Even then the configure and link steps are single threaded.

Interesting. Ryzen 7 5800H with 28GB (It looks like 4 of my 32 are eaten by the iGPU):

Code: Select all

     Thu Sep 22 23:25:22 2022 >>> www-client/firefox-105.0
       merge time: 20 minutes and 54 seconds.

     Sun Sep 25 18:42:12 2022 >>> www-client/firefox-105.0.1
       merge time: 21 minutes and 16 seconds.

     Sat Oct  8 21:42:00 2022 >>> www-client/firefox-105.0.2
       merge time: 21 minutes and 55 seconds.

     Sun Oct 16 01:56:22 2022 >>> www-client/firefox-105.0.2
       merge time: 19 minutes and 56 seconds.

     Thu Dec 29 20:10:30 2022 >>> www-client/firefox-102.6.0
       merge time: 18 minutes and 20 seconds.

     Wed Jan 18 22:00:51 2023 >>> www-client/firefox-102.7.0
       merge time: 19 minutes and 4 seconds.

     Sun Jan 22 09:31:32 2023 >>> www-client/firefox-102.7.0
       merge time: 17 minutes and 55 seconds.

     Thu Mar 30 15:25:01 2023 >>> www-client/firefox-111.0
       merge time: 18 minutes and 40 seconds.

     Wed Apr 12 21:33:45 2023 >>> www-client/firefox-112.0
       merge time: 22 minutes and 59 seconds.

     Wed Apr 19 19:41:09 2023 >>> www-client/firefox-112.0.1
       merge time: 18 minutes and 3 seconds.

     Sun Apr 30 13:32:33 2023 >>> www-client/firefox-112.0.2
       merge time: 16 minutes and 51 seconds.

     Wed May 10 17:50:33 2023 >>> www-client/firefox-113.0
       merge time: 17 minutes and 5 seconds.

     Thu May 18 13:26:31 2023 >>> www-client/firefox-113.0.1
       merge time: 17 minutes and 1 second.

     Sun May 28 09:39:18 2023 >>> www-client/firefox-113.0.2
       merge time: 17 minutes and 6 seconds.

     Thu Jun  8 11:58:18 2023 >>> www-client/firefox-114.0
       merge time: 17 minutes and 45 seconds.

It's a laptop, I've never seen it exceed 85W power consumption.

Best Regards,
Georgi

C5ace · Post by **C5ace** » Tue Jun 27, 2023 7:15 am

Ryzen 9 3950X, 16-Core, 32 Treads Processor, 64Gb RAM, No Overclocking, Rotating Rust:

qlop -v while running Xfce:

Code: Select all

022-11-06T08:10:12 >>> www-client/firefox-102.4.0: 18′02″
2022-11-18T14:54:57 >>> www-client/firefox-102.5.0: 14′41″
2022-11-24T10:31:19 >>> www-client/firefox-102.5.0: 14′05″
2022-11-27T23:01:52 >>> www-client/firefox-102.5.0: 14′04″
2022-12-18T08:48:27 >>> www-client/firefox-102.6.0: 14′11″
2023-01-15T22:30:05 >>> www-client/firefox-102.6.0: 13′07″
2023-01-18T08:59:24 >>> www-client/firefox-102.7.0: 13′35″
2023-02-13T14:45:14 >>> www-client/firefox-102.7.0: 13′34″
2023-02-15T09:28:41 >>> www-client/firefox-102.7.0-r1: 13′53″
2023-02-22T10:21:09 >>> www-client/firefox-102.8.0: 13′45″
2023-03-18T09:25:45 >>> www-client/firefox-102.9.0: 13′53″
2023-04-13T08:31:07 >>> www-client/firefox-102.10.0: 15′18″
2023-05-05T08:04:16 <<< www-client/firefox-102.10.0: 3s
2023-05-05T09:04:28 >>> www-client/firefox-102.10.0: 13′00″
2023-05-12T18:28:48 >>> www-client/firefox-102.11.0: 12′17″
2023-05-30T10:55:38 >>> www-client/firefox-102.11.0: 12′14″
2023-06-03T10:12:33 >>> www-client/firefox-102.11.0: 12′41″
2023-06-09T10:37:50 >>> www-client/firefox-102.12.0: 12′43″

nikolis · Post by **nikolis** » Tue Jun 27, 2023 9:21 am

/Nic # qlop firefox

Code: Select all

2023-06-09T23:57:22 >>> www-client/firefox: 11′57″

Code: Select all

OS: Gentoo Linux x86_64 
     Kernel: 6.1.22-gentoo-dist 
          DE: GNOME 44.1
       CPU: AMD Ryzen 7 7700X (16) @ 4.500GHz
  Memory: 3100MiB / 63427MiB

Post by **NeddySeagoon** » Tue Jun 27, 2023 9:43 am

nikolis,

I run emerge with --jobs=3 and MAKEOPTS="-j32". I put up with the slowdown when firefox, thunderbird and libreoffice build concurrently, as it does not interfere with interactive use. It does not happen often.
So yes, its quite likely that other builds were happening concurrently.

nikolis · Post by **nikolis** » Tue Jun 27, 2023 9:53 am

figueroa wrote:nikolis -- Use the command:
Code: Select all
qlop firefox
to see emerge time history on your machine. qlop is part of app-portage/portage-utils.

I didn't know about qlop, thanks. i usually use

Code: Select all

genlop -t

nikolis · Post by **nikolis** » Tue Jun 27, 2023 10:13 am

NeddySeagoon wrote:nikolis,

I run emerge with --jobs=3 and MAKEOPTS="-j32". I put up with the slowdown when firefox, thunderbird and libreoffice build concurrently, as it does not interfere with interactive use. It does not happen often.
So yes, its quite likely that other builds were happening concurrently.

Understood.