From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 55CCE139083 for ; Wed, 22 Nov 2017 12:16:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B3F90E0D4E; Wed, 22 Nov 2017 12:16:22 +0000 (UTC) Received: from smarthost03b.mail.zen.net.uk (smarthost03b.mail.zen.net.uk [212.23.1.21]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 55A80E0CCD for ; Wed, 22 Nov 2017 12:16:21 +0000 (UTC) Received: from [82.69.80.10] (helo=peak.localnet) by smarthost03b.mail.zen.net.uk with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1eHTwy-0004VD-E1 for gentoo-user@lists.gentoo.org; Wed, 22 Nov 2017 12:16:20 +0000 From: Peter Humphrey 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 Message-ID: <3557375.BispIgJljk@peak> In-Reply-To: <20171122085729.xj3rkajouubpvu6v@grusum.endjinn.de> References: <6b5fbeca-453c-f103-5e4e-a8db83a6dabf@st.com> <2631935.PigJGvPPt2@eve> <20171122085729.xj3rkajouubpvu6v@grusum.endjinn.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03b-IP: [82.69.80.10] Feedback-ID: 82.69.80.10 X-Archives-Salt: 5979684b-879f-4289-a3a2-57c9c020d7e6 X-Archives-Hash: 80b059102b10c16e154b1149a5324fae 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.