From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge -j, make -j and make -l
Date: Sun, 27 Nov 2011 05:52:18 -0500 [thread overview]
Message-ID: <CA+czFiD=A8L6+ZM0cVZGuFdWBY6S+o1FbvsOXamU-dadjcH3TA@mail.gmail.com> (raw)
In-Reply-To: <19356.1322390348@ccs.covici.com>
On Sun, Nov 27, 2011 at 5:39 AM, <covici@ccs.covici.com> wrote:
> Mick <michaelkintzios@gmail.com> wrote:
>
>> On Saturday 26 Nov 2011 15:22:15 Michael Mol wrote:
>> > I just wanted to share an experience I had today with optimizing parallel
>> > builds after discovering "-l" for Make...
>> >
>> > I've got a little more tweaking I still want to do, but this is pretty
>> > awesome...
>> >
>> > http://funnybutnot.wordpress.com/2011/11/26/optimizing-parallel-builds/
>> >
>> > ZZ
>>
>> Thanks for sharing! How do you determine the optimum value for -l?
>
> How do you get emerge not to display number of jobs and load average --
The display is something emerge will show you if you've asked it to
build in parallel (which you did, by passing -j to emerge. That's
different from putting -j in MAKEOPTS.)
> I only want to compile one at a time -- much safer that way and it is
> doing that,
It's likely only doing that because there isn't anything it can
immediately build that doesn't have what it's *currently* working on
as a build dependency. I noted in my blog post that emerge's
parallelization has many of the same limitations as make's that's one
of the things I was talking about; there can be linchpin and keystone
packages which need to be built before many others. libc would be an
example. gcc is a frequent example.
> but now it displays all that load average and how many jobs,
> etc. -- any way to get rid of that display?
Forget the display; it sounds like you don't want emerge building in
parallel. In that event, don't pass "-j" to emerge. The display will
go away.
--
:wq
next prev parent reply other threads:[~2011-11-27 10:53 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 15:22 [gentoo-user] emerge -j, make -j and make -l Michael Mol
2011-11-26 15:34 ` Alex Schuster
2011-11-26 15:51 ` Michael Mol
2011-11-26 16:03 ` Stefan G. Weichinger
2011-12-19 19:58 ` Stefan G. Weichinger
2011-12-19 20:05 ` Michael Mol
2011-11-26 15:35 ` Stefan G. Weichinger
2011-11-27 9:27 ` Mick
2011-11-27 10:09 ` Michael Mol
2011-11-27 17:56 ` Pandu Poluan
2011-11-27 20:16 ` Michael Mol
2011-11-27 20:42 ` Michael Mol
2011-11-27 20:51 ` Alex Schuster
2011-11-28 0:42 ` Pandu Poluan
2011-11-27 20:57 ` Alan McKinnon
2011-11-28 1:06 ` Pandu Poluan
2011-11-28 5:30 ` Michael Mol
2011-11-28 5:55 ` Pandu Poluan
2011-11-27 23:21 ` Neil Bothwick
2011-11-28 0:54 ` Pandu Poluan
2011-11-28 1:10 ` [gentoo-user] " Jack Byer
2011-11-28 1:35 ` Dale
2011-11-28 2:16 ` Pandu Poluan
2011-11-28 7:02 ` Dale
2011-11-28 4:34 ` [gentoo-user] " Michael Mol
2011-11-28 5:13 ` Pandu Poluan
2011-11-28 5:27 ` Michael Mol
2011-11-28 9:27 ` Neil Bothwick
2011-11-28 13:36 ` Pandu Poluan
2011-11-28 16:36 ` Stefan G. Weichinger
2011-11-29 11:08 ` Neil Bothwick
2011-11-29 13:47 ` Stefan G. Weichinger
2011-11-29 15:39 ` Neil Bothwick
2011-11-29 18:50 ` Stefan G. Weichinger
2011-11-28 4:30 ` Michael Mol
2011-11-27 10:39 ` covici
2011-11-27 10:52 ` Michael Mol [this message]
2011-11-27 10:58 ` Dale
2011-11-27 14:47 ` covici
2011-11-27 15:02 ` Dale
2011-11-27 15:25 ` covici
2011-11-27 17:26 ` Michael Hampicke
2011-11-27 17:46 ` Pandu Poluan
2011-11-27 22:07 ` Mark Knecht
2011-11-27 23:13 ` Dale
2011-11-28 4:28 ` Michael Mol
2011-11-28 5:26 ` Pandu Poluan
2011-11-28 9:27 ` Neil Bothwick
2011-11-28 10:22 ` Pandu Poluan
2011-11-28 13:03 ` Jorge Martínez López
2011-11-28 13:26 ` Pandu Poluan
2011-11-28 18:51 ` Michael Mol
2011-11-28 18:54 ` Michael Mol
2011-11-28 23:53 ` Michael Mol
2011-12-10 4:35 ` Michael Mol
2011-12-27 15:16 ` Michael Mol
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='CA+czFiD=A8L6+ZM0cVZGuFdWBY6S+o1FbvsOXamU-dadjcH3TA@mail.gmail.com' \
--to=mikemol@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