From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] long compiles
Date: Tue, 12 Sep 2023 22:08:49 +0100 [thread overview]
Message-ID: <dddd5a56-9fcc-d75f-6e78-69398478919c@youngman.org.uk> (raw)
In-Reply-To: <CAEdtoraZKj=OhZy8qdTV+shW0VF2TfLCVZbbRCThASFUcrpbfw@mail.gmail.com>
On 11/09/2023 20:46, Alan McKinnon wrote:
> qtwebengine! yes that one took forever also. It also said my 16G of RAM
> was smaller than the 16G it needed. Weird.
>
> Anyways I enabled a swapfile and left it to run overnight
16GB physical ram <> 16GB usable ram for the compile ...
I concur with others that tmpfs is the way to go - I don't think my
system is set up that way just now, but I always have googols of swap
(twice max physical ram per disk) so I just declare a huge ramdisk for
compiling on.
My current system has four ram slots, two maxed out with 16GB chips
each, so that makes 128GB swap partitions per disk (4 of them) equals
512GB swap ...
(Yes the people at openSUSE said I was being stupid with that much swap)
But declare a 128GB ramdisk, and it'll spill over as required, but
anything that fits in ram will compile very quick.
And yes, I also used to have my systems configured so they had one
shared portage area, matching make.conf, and were set up to "use binary
if it exists, else build one". I had the opposite problem though, my
nice fast system had a habit of crashing, so I used the old slow one to
build most things, because it was more reliable. Hey ho.
There's all sorts of tricks, some work for some people, others work for
others.
Cheers,
Wol
next prev parent reply other threads:[~2023-09-12 21:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 19:19 [gentoo-user] long compiles Alan McKinnon
2023-09-11 19:31 ` Dale
2023-09-11 19:33 ` Siddhanth Rathod
2023-09-11 19:46 ` Alan McKinnon
2023-09-12 21:08 ` Wol [this message]
2023-09-13 11:28 ` Peter Humphrey
2023-09-13 11:50 ` Wols Lists
2023-09-13 12:38 ` Frank Steinmetzger
2023-09-13 12:41 ` Peter Humphrey
2023-09-13 15:14 ` Michael
2023-09-14 9:49 ` Peter Humphrey
2023-09-14 12:24 ` Michael
2023-09-11 19:42 ` Ramon Fischer
2023-09-11 19:46 ` Ramon Fischer
2023-09-11 20:05 ` Neil Bothwick
2023-09-11 20:21 ` Alan McKinnon
2023-09-11 21:22 ` Michael
2023-09-11 21:46 ` Alan McKinnon
2023-09-11 23:04 ` Ramon Fischer
2023-09-12 8:57 ` Alan McKinnon
2023-09-12 10:14 ` Peter Humphrey
2023-09-12 10:57 ` Jacques Montier
2023-09-12 9:26 ` [gentoo-user] " Nikos Chantziaras
2023-09-12 9:19 ` Nikos Chantziaras
2023-09-12 19:01 ` Alan McKinnon
2023-09-12 19:30 ` Nuno Silva
2023-09-12 22:11 ` Neil Bothwick
2023-09-13 21:15 ` [gentoo-user] " Kristian Poul Herkild
2023-09-13 21:20 ` [gentoo-user] " Grant Edwards
2023-09-13 21:37 ` Neil Bothwick
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=dddd5a56-9fcc-d75f-6e78-69398478919c@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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