public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] is multi-core really worth it?
Date: Wed, 22 Nov 2017 01:21:07 -0600	[thread overview]
Message-ID: <CAAD4mYjgrXLLMR7D-XLHkWqOCOR2Y1GDVpnvO3NjKobzUhzSrw@mail.gmail.com> (raw)
In-Reply-To: <6b5fbeca-453c-f103-5e4e-a8db83a6dabf@st.com>

Hello,

On Wed, Nov 22, 2017 at 12:52 AM, Raffaele Belardi
<raffaele.belardi@st.com> wrote:
> Hi,
>
> rebuilding system and world with gcc-7.2.0 on a 6-core AMD CPU I have the impression that
> most of the ebuilds limit parallel builds to 1, 2 or 3 threads. I'm aware it is only an
> impression, I did not spend the night monitoring the process, but nevertheless every time
> I checked the load was very low.
>

Assuming all of your compilation is on a RAM disk, there are two main
bottlenecks that are easy to spot: network access (downloading new
packages) and dependency chokepoints (packages must be compiled in a
chain). Other potential chokepoints like disk access are negligible in
my experience, though for one merge I did have two or three ebuilds
fighting for disk IO "lock up" a system.

If all dependencies have been satisfied on your system I invite you to
merge a bunch of packages at once (@world?), you should notice greater
parallelism.

> Does anyone have real-world statistics of CPU usage based on gentoo world build?
>

I've considered ways to gather these statistics off and on over the
years, but it is easy to start sinking a lot of time into it. It is
possible the data you want exists, but I have not found any extant
solution involving portage that provides that detail of logging.*

Cheers,
     R0b0t1


* Someone will prove me wrong in 3... 2... 1...


  reply	other threads:[~2017-11-22  7:21 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 [this message]
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
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=CAAD4mYjgrXLLMR7D-XLHkWqOCOR2Y1GDVpnvO3NjKobzUhzSrw@mail.gmail.com \
    --to=r030t1@gmail.com \
    --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