From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] is multi-core really worth it?
Date: Mon, 4 Dec 2017 22:17:18 -0600 [thread overview]
Message-ID: <CAAD4mYi_FYiNeMHSq2ziv9dBezwOZRiGTvxMX17P3Qt2PodbzA@mail.gmail.com> (raw)
In-Reply-To: <f50301da-6138-ae94-5d45-658f09faf9cd@gmx.com>
On Mon, Dec 4, 2017 at 10:11 PM, Taiidan@gmx.com <Taiidan@gmx.com> wrote:
> On my 16 core opteron I have to do -j32 or sometimes -j64 to be using
> everything all the time, is this normal? If I don't do this it won't be
> pegged at 100% all the time.
>
I use a ramdisk and anything over -j${NCPU} (incl. hyperthreaded
cores) causes performance degradation in general due mainly to the
compiling step. For some package sets I have noticed that higher build
parallelism helps due to some ebuild steps not being easily
parallelizable.
> I assume using a ramdisk would help with this? I wouldn't want to do a SSD
> as I assume it would excessively wear by doing compiles.
>
It should. While builds on an SSD will wear the SSD, comparing the
write volume to the expected drive lifetime will tell you the true
impact. It is (if I remember) still relatively small.
Cheers,
R0b0t1
next prev parent reply other threads:[~2017-12-05 4:17 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 [this message]
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=CAAD4mYi_FYiNeMHSq2ziv9dBezwOZRiGTvxMX17P3Qt2PodbzA@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