From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] is multi-core really worth it?
Date: Wed, 22 Nov 2017 12:16:20 +0000 [thread overview]
Message-ID: <3557375.BispIgJljk@peak> (raw)
In-Reply-To: <20171122085729.xj3rkajouubpvu6v@grusum.endjinn.de>
On Wednesday, 22 November 2017 08:57:29 GMT David Haller wrote:
> Hello,
>
> On Wed, 22 Nov 2017, J. Roeleveld wrote:
> >On Wednesday, November 22, 2017 8:48:08 AM CET David Haller wrote:
> >> So, your emerge is mostly IO and "emerge"-threads bound. Solution:
> >> adjust your build-threads[1], and then adjust your emerge jobs! See
> >> '--jobs' in 'man emerge'. Can't find where to set a default in a
> >> config-file for that ATM, but you could always alias/function/script
> >
> >> emerge to something else, e.g. put this in your ~/.bashrc:
> >Instead of all these aliases, simply edit your make.conf ( /etc/portage/
> >make.conf )
> >
> >And edit (or add) the following lines:
> >MAKEOPTS="--jobs 24 --load-average 48"
> >EMERGE_DEFAULT_OPTS="--jobs 24 --load-average 48"
>
> Well, that alias/function/script is mostly for all the other (default)
> options I want ;) Hm. What's this EMERGE_DEFAULT_OPTS though? ;)) And
> how can I override them if not wanted? .oO( gotta read up on that )Oo.
Options passed on the command line (as in an alias) override any others. I
assume a function would be equivalent to an alias here, but I haven't
checked as I don't use them.
There used to be debates on the efficiency of alias versus function, but if
they're only taking nanoseconds to execute, what does it matter?
--
Regards,
Peter.
next prev parent reply other threads:[~2017-11-22 12:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 6:52 [gentoo-user] is multi-core really worth it? Raffaele Belardi
2017-11-22 7:21 ` R0b0t1
2017-11-22 7:26 ` Jeremi Piotrowski
2017-11-22 8:23 ` Neil Bothwick
2017-11-22 8:34 ` David Haller
2017-11-22 10:07 ` [gentoo-user] " Martin Vaeth
2017-11-22 11:26 ` David Haller
2017-11-23 22:47 ` Martin Vaeth
2017-11-22 13:12 ` [gentoo-user] " Raffaele Belardi
2017-11-22 13:23 ` J. Roeleveld
2017-11-22 14:11 ` Tsukasa Mcp_Reznor
2017-11-22 14:34 ` Wols Lists
2017-11-22 16:27 ` J. Roeleveld
2017-12-05 4:11 ` Taiidan
2017-12-05 4:17 ` R0b0t1
2017-12-05 10:09 ` Peter Humphrey
2017-12-05 10:46 ` Wols Lists
2017-12-05 11:13 ` Raffaele Belardi
2017-12-05 11:39 ` Mick
2017-12-05 13:07 ` Peter Humphrey
2017-12-05 13:57 ` Wols Lists
2017-12-05 14:13 ` Peter Humphrey
2017-12-05 21:56 ` Neil Bothwick
2017-12-06 13:29 ` Wols Lists
2017-12-06 15:34 ` Alan McKinnon
2017-12-06 16:07 ` Wols Lists
2017-12-06 23:51 ` [gentoo-user] " Ian Zimmerman
2017-12-06 16:12 ` [gentoo-user] " Wols Lists
2017-12-06 17:24 ` Kai Peter
2017-11-22 7:48 ` David Haller
2017-11-22 8:32 ` J. Roeleveld
2017-11-22 8:57 ` David Haller
2017-11-22 12:16 ` Peter Humphrey [this message]
2017-11-22 16:36 ` Neil Bothwick
2017-11-28 10:07 ` [gentoo-user] " Raffaele Belardi
2017-12-01 10:39 ` J. Roeleveld
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=3557375.BispIgJljk@peak \
--to=peter@prh.myzen.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