public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] is multi-core really worth it?
Date: Wed, 22 Nov 2017 14:23:06 +0100	[thread overview]
Message-ID: <5126763.L5XyAvMajf@eve> (raw)
In-Reply-To: <85555669-e101-e17e-9486-090afbb52784@st.com>

On Wednesday, November 22, 2017 2:12:31 PM CET Raffaele Belardi wrote:
> Jeremi Piotrowski wrote:
> > That being said: if you do a world rebuild you will have lots of packages
> > that spend ~40 seconds doing their autoconf run, only to build 2-3 sources
> > files. On an 8-core machine at work, I get good results using parallel
> > emerge jobs (emerge -jX). For your 6-core AMD CPU (assuming it actually
> > has 12 threads) I'd start with 'emerge -j3' and MAKEOPTS='-j12 -l16'.
> > That should get you a nice speedup, but may require a bit more ram.
> 
> emerge -j3 is something I did not think of, I'll try it. But won't that
> break portage's carefully crafted package dependencies? I suppose you could
> get occasional build failures?

No, it won't.
If it has multiple packages that can be built (taking dependencies into 
account) it will. If all packages in the queue are waiting for a single 
package to be installed, all those will wait till that package is finished.

> I'm using MAKEOPTS=-j7, I thought 2 threads per CPU (hyperthreading?) was an
> Intel thing only.

I thought so too.

Don't forget to add the "load-average" option to both, otherwise there is a 
very likely chance you will have 3 * 7 = 21 build processes running at the 
same time.

Also, I have had situations where using "-j" actually caused some issues where 
it was picked up by the wrong process or it has a different meaning for some 
other process. Specifying the long version (--jobs) has been reliable for me.

--
Joost


  reply	other threads:[~2017-11-22 13:23 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 [this message]
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
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=5126763.L5XyAvMajf@eve \
    --to=joost@antarean.org \
    --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