public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems with MAKEOPTS -j
Date: Thu, 25 Aug 2011 08:16:45 -0500	[thread overview]
Message-ID: <4E564B3D.4050901@gmail.com> (raw)
In-Reply-To: <CA+czFiDEv+Rubx7y=RjTM=ihJbTXCEXfD-G7zvbd2373xemWug@mail.gmail.com>

Michael Mol wrote:
> Sometimes. My understanding is that it comes from packages which are
> badly constructed, and can't reliably handle parallel builds. I'm told
> that these cases are bugs and should be reported. Sometimes, if I
> watch build output fly by, I'll even see something like
>
> make -j10 -j1 (some target name)
>
> where a maintainer decided to put an overriding -j1 after MAKEOPTS.
>
>
> About two years ago, I found that, on my system (quad-core AMD Phenom
> 9650), -j8 resulted in the fastest build time, as measured by building
> ffmpeg.[1] Currently, I'm running -j10, and that's because I've been
> using distcc to pass a couple compile tasks off to other systems.
> (Though with the box I was deferring to scrapped for parts, I'll drop
> this down to -j8 again)
>
> [1] Tested by building in tmpfs. You can find my data here:
> http://multimedia.cx/eggs/ffmpeg-and-multiple-build-threads/#comment-150325
>
>    

This is interesting.  I changed mine to j8 too.  See how this works.  
CPUs are so fast nowadays, they can do a lot pretty fast.  I'm trying to 
imagine 10 years from now.  O_O

Dale

:-)  :-)



  reply	other threads:[~2011-08-25 13:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  7:37 [gentoo-user] Problems with MAKEOPTS -j Pandu Poluan
2011-08-25  7:46 ` Joost Roeleveld
2011-08-25  7:54   ` Dale
2011-08-25 12:06 ` Michael Mol
2011-08-25 13:16   ` Dale [this message]
2011-08-25 13:33     ` Michael Mol
2011-08-25 13:38     ` Peter Humphrey
2011-08-25 14:46       ` Dale
2011-08-25 14:18 ` Paul Hartman

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=4E564B3D.4050901@gmail.com \
    --to=rdalek1967@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