4GB is barely enough. But you can limit the compilation threads to save memory. For big compilations you should reserve around 1.5GB per compilation thread.

As for celeron... You'd better use binary host, at least for big packages (or have your own binary host).

Here I have one old Chromebox for which I flashed coreboot into.

2024-03-13T09:59:14 >>> net-libs/nodejs-20.11.0: 3:36:15
2024-05-10T05:02:52 >>> net-libs/nodejs-20.12.1: 6:12:09
2024-10-01T00:25:35 >>> net-libs/nodejs-22.4.1-r1: 7:24:58
2024-12-26T01:43:48 >>> net-libs/nodejs-22.4.1-r1: 15:32:58

The three first lines show compilation times of nodejs with quite normal compilation settings. On the last line I enabled some ridiculous optimizations, like -funroll-loops and -fipa-pta but also -lto (which probably contributes the most of the compilation time increase). I've retired this box now, but I might give it a new life as some home automation box.

Obligatory fastfetch.

panther-box ~ # fastfetch --logo none
root@panther-box
----------------
OS: Gentoo 2.17 x86_64
Host: Panther (1.0)
Kernel: Linux 6.1.110-panther-0.3.1
Uptime: 36 days, 18 hours, 10 mins
Packages: 701 (emerge)
Shell: bash 5.2.37
Theme: Adwaita [GTK3]
Icons: gnome [GTK3]
Cursor: Adwaita
Terminal: tmux 3.4
CPU: Intel(R) Celeron(R) 2955U (2) @ 1.40 GHz
GPU: Intel Haswell-ULT Integrated Graphics Controller @ 1.00 GHz [Integrated]
Memory: 950.19 MiB / 15.50 GiB (6%)
Swap: 7.00 MiB / 20.00 GiB (0%)
Disk (/): 13.37 GiB / 14.94 GiB (90%) - xfs
Disk (/home): 133.21 MiB / 1.94 GiB (7%) - xfs
Disk (/var): 1.57 GiB / 1.94 GiB (81%) - xfs
Disk (/var/cache/pkg): 12.98 GiB / 19.94 GiB (65%) - xfs

... and because I had some 8GB DDR3 SODIMM RAM sticks I stuffed the maximum amount in there. If I was on 4GB, I'd use binhost or tune the compilation settings so that the process would use as little memory as possible.

It took me 6-8 hours to install. Started 12-13 ended in 19 hours.

Yes.

I mean, it can be faster than your average distro on some scenarios. Mostly if you know your way in kernel config.

Though most of its real advantages are in the form of a lean system completely tailored to your needs.

It seems to me most of that Gentoo FUD comes from people that never even tried to install it or gave up because apparently reading a wiki is too hard for them.

Binary speed is really the least reason to do it. Whether it's worth it or not is up to the individual, but there are a lot of little reasons Gentoo is uniquely powerful.

Benefits specific to compiling:

• fine-grained control of features and dependencies with USE flags
• very easy package maintenance (writing ebuilds)
  • much simpler to add your own custom local packages when you need them
  • less workload on the gentoo team which is good for repository health and breadth
• control of compile flags (yes speed, but more practically hardening for secure systems)
• the same gentoo is available on way more platforms and architectures than any binary distro

Askey myself the same and found it here

Thanks, I just searched on ddg purple anime wallpaper and found this https://wallpapersden.com/happiest-anime-girl-hd-ai-art-wallpaper/

https://images.wallpapersden.com/image/download/happiest-anime-girl-hd-ai-art_bmVsZmyUmZqaraWkpJRmbmpnrWZmZ2U.jpg

Yeah, battery broken, it's constantly on AC or DC idk I'm not electrician.

Thanks, surpassingly, it didn't take long around 6-8 hours. I started at around 12-13 and ended at 19. I did kind of speed run installation and did as fast as possible. I first tried installing gnome or kde, but compiling was too long, so I decided xfce.