this post was submitted on 26 Dec 2024
100 points (98.1% liked)
Unixporn
15538 readers
79 users here now
Unixporn
Submit screenshots of all your *NIX desktops, themes, and nifty configurations, or submit anything else that will make themers happy. Maybe a server running on an Amiga, or a Thinkpad signed by Bjarne Stroustrup? Show the world how pretty your computer can be!
Rules
- Post On-Topic
- No Defaults
- Busy Screenshots
- Use High-Quality Images
- Include a Details Comment
- No NSFW
- No Racism or use of racist terms
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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
.... 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.
Homie UPTIME IS 36 DAYS?!?? what does this computer do???? ๐๐๐๐