From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Change MAKEOPTS on the fly?
Date: Mon, 13 Jul 2020 17:33:45 +0100 [thread overview]
Message-ID: <20200713173345.1a634589@digimed.co.uk> (raw)
In-Reply-To: <536c8058fe8a42cfaf38ba600576dd92a90004eb.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Mon, 13 Jul 2020 11:10:01 -0500, Matt Connell (Gmail) wrote:
> > Another thing I recommend is getting rid of "-j5". Use -j4. The "+1"
> > recommendation from decades ago does not apply anymore with modern
> > Linux kernels. You can test this yourself by emerging a smaller
> > package that takes like 2 minutes or so to emerge, and compare times
> > with j4 and j5. Most likely you will see no difference, other than j5
> > using more RAM.
>
> I can confirm this as well. On RAM-limited systems (like this laptop
> with 8 logical cores and only 8GB of memory...) I have to use "-j2" in
> order to keep the machine usable while compiling.
You have to consider the --jobs option passed to emerge at the same time.
It's no use limiting each emerge to 2 processes if you then run multiple
emerges in parallel. Setting --load in MAKEOPTS and --load-average in
EMERGE_DEFAULT_OPTS is worthwhile on a constrained system.
--
Neil Bothwick
Knock firmly but softly. I like soft firm knockers.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-13 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 6:04 [gentoo-user] Change MAKEOPTS on the fly? William Kenworthy
2020-07-12 8:29 ` [gentoo-user] " Nikos Chantziaras
2020-07-12 8:54 ` tastytea
2020-07-12 9:58 ` Nikos Chantziaras
2020-07-12 8:59 ` Michael
2020-07-12 10:03 ` Nikos Chantziaras
2020-07-12 11:38 ` William Kenworthy
2020-07-12 12:39 ` Michael
2020-07-13 16:10 ` Matt Connell (Gmail)
2020-07-13 16:33 ` Neil Bothwick [this message]
2020-07-13 16:50 ` Matt Connell (Gmail)
2020-07-13 17:43 ` Neil Bothwick
2020-07-13 23:34 ` Sam Jorna (wraeth)
2020-07-13 23:56 ` Sam Jorna (wraeth)
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=20200713173345.1a634589@digimed.co.uk \
--to=neil@digimed.co.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