public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Toshinori Endo <endo.toshinori@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] MAKEOPTS values for Athlon 64 X2
Date: Mon, 15 Jan 2007 18:17:48 +0900	[thread overview]
Message-ID: <45AB46BC.2040402@gmail.com> (raw)
In-Reply-To: <45AB1451.9010005@paulscrap.com>

Hello PaulNM,


PaulNM wrote:
> Hey folks,
>
>     I'm wondering if anyone has experimented with different values for 
> MAKEOPTS="-jx" on Athlon 64 X2's.  The guides usually suggest # of 
> cores/processors plus one. Looking at "man make.conf" doesn't help 
> much, it just says "Suggested settings are between CPUs+1 and  
> 2*CPUs+1". The only thing "man make" mentions about  the "-j" option 
> is "If the -j option is given without an argument, make  will  not 
> limit the number of jobs that can run simultaneously." I've also seen 
> some mentions of -j9 by people with dual core systems elsewhere, 
> indicating it drastically speed up some emerges.
>
>     So this leaves me with several possibilities. There's -j3 (current 
> setting), -j5, -j (no limit), -j9, or some other random number. Any 
> suggestions/warnings/links would be appreciated.
>
> Thanks,
>     PaulNM
>

On my 4x Dual-Core Opteron system, -j9 actually worked as expected, but 
not as much on the other system with two CPUs.

Is that what you want?

Here is the story.
The value of MAKEOPTS including -jx is passed to the `make' command so 
that x kid jobs at most can be executed.  If 1+#CPU is given as the 
parameter, each CPU is assigned a single kid process because make 
command itself does have much to do while the kids are working hard.  
Giving the larger number just let them do extra job to switch among kids 
in expense of performance down.

te
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-01-15  9:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15  5:42 [gentoo-amd64] MAKEOPTS values for Athlon 64 X2 PaulNM
2007-01-15  9:17 ` Toshinori Endo [this message]
2007-01-15 15:39 ` Thomas Rösner
2007-01-15 18:10   ` [gentoo-amd64] " Duncan
2007-01-15 23:32     ` Thomas Rösner
2007-01-16  8:28       ` Andrei Slavoiu
2007-01-16 10:27         ` Neil Bothwick
2007-01-16 16:15           ` Peter Humphrey
2007-01-17  2:41         ` Thomas Rösner
2007-01-17  7:47           ` Duncan
2007-01-17 12:34             ` Boyd Stephen Smith Jr.
2007-01-17 17:24             ` Hemmann, Volker Armin
2007-01-17 19:02               ` Bernhard Auzinger
2007-01-17 21:22                 ` Hemmann, Volker Armin
2007-01-18  4:50                   ` Duncan
2007-01-18 16:12                     ` Hemmann, Volker Armin
2007-01-18 16:16                       ` Rob Lesslie
2007-01-18 18:10                         ` Boyd Stephen Smith Jr.
2007-01-18 18:35                           ` Simon Stelling
2007-01-18 19:13                             ` Boyd Stephen Smith Jr.
2007-01-18 19:51                               ` Simon Stelling
2007-01-26  8:49                             ` Peter Humphrey
2007-01-26 23:18                               ` Thomas Rösner
2007-01-18 18:41                       ` Duncan
2007-01-18 18:51                         ` Hemmann, Volker Armin
2007-01-18 19:17                           ` Duncan
2007-01-18 19:36                     ` Bob Young
2007-01-18 19:42                       ` Harry Holt
2007-01-19  7:57                         ` Duncan
2007-01-26  0:46                     ` Peter Humphrey
2007-01-16 11:11       ` Duncan

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=45AB46BC.2040402@gmail.com \
    --to=endo.toshinori@gmail.com \
    --cc=gentoo-amd64@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