In the single core cpu hdd era it was common to compile with -j2 to minimize waiting for IO.
Maybe a fistfull of extra jobs could help?
Announcement
Collapse
No announcement yet.
Building The Default x86_64 Linux Kernel In Just 16 Seconds
Collapse
X
-
Originally posted by nils_ View PostI wonder though if most files aren't cached already anyways - the impact may not be as noticeable as some think.
- Likes 2
Leave a comment:
-
Originally posted by nils_ View PostI wonder though if most files aren't cached already anyways - the impact may not be as noticeable as some think.
Tried it on my poor Xeon 3470 4c/8t, 24 GB for amd-staging-drm-next.
Only some seconds if any.
- Likes 3
Leave a comment:
-
I wonder though if most files aren't cached already anyways - the impact may not be as noticeable as some think.
- Likes 3
Leave a comment:
-
Yeah, I've had /var/tmp/portage as a tmpfs on my Gentoo boxes for forever. This is a big motivation for getting at least 32gb if ram in them as building chromium nowadays can chew up close to 12gb of disk during the build. And yeah, Zen2 is a monster for compiling code - Yesterday I recompiled everything on my new 3900x Gentoo media server with GCC-9.2 and znver2 (the ebuild showed up in portage yesterday) and ~1100 packages only took about 7hrs to build.
- Likes 2
Leave a comment:
-
Originally posted by nanonyme View Post
Meh, that sounds nasty. People usually assume /var/tmp persists over reboot.
It's in Gentoo doc.
- Likes 1
Leave a comment:
-
Originally posted by RavFX View PostMichael How many gentooer do you know?
My whole distrib is built in a tmpfs.
All the other gentooer friends I know have configured it like that because... it's faster.
Actually more funny, the only thing that I don't build in a tmpfs, is the kernel, because the tmpfs is /var/tmp (for portage building shenanigans)
- Likes 2
Leave a comment:
-
It would be nice to know how long this takes on NVMe and AHCI drives as well.
But wow!
- Likes 1
Leave a comment:
Leave a comment: