public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH v2] Default MAKEOPTS to -j(ncpus+1) when unset
Date: Thu, 29 Jan 2015 23:05:31 -0800	[thread overview]
Message-ID: <54CB2D3B.7050202@gentoo.org> (raw)
In-Reply-To: <54C9A3A5.9090308@gentoo.org>

On 01/28/2015 07:06 PM, Rick "Zero_Chaos" Farina wrote:
> On 01/18/2015 11:58 AM, Brian Dolbec wrote:
>> On Sun, 18 Jan 2015 11:38:38 +0100
>> Michał Górny <mgorny@gentoo.org> wrote:
>>
>>> Default MAKEOPTS job number to (number of CPUs + 1) when it is not
>>> provided in the ebuild environment.
>>>
>>> Suggested-By: Daniel Robbins <drobbins@funtoo.org>
>>> ---
>>>  pym/portage/package/ebuild/doebuild.py |  8 +++++++-
>>>  pym/portage/util/cpuinfo.py            | 18 ++++++++++++++++++
>>>  2 files changed, 25 insertions(+), 1 deletion(-)
>>>  create mode 100644 pym/portage/util/cpuinfo.py
>>>
>>
>>
>> looks good, merge please
>>
> I realize I'm a little bit late here, but after extensive testing with
> multiple different schedulers that NUMCPU provides equivalent
> performance, or even outperforms NUMCPU+1.  I think that changes from 1
> cpu to NUMCPU is good enough, and we don't need to test thrashing the
> scheduler.

Yeah, that's what I was thinking when the patch was submitted, but I
forgot to mention it.
-- 
Thanks,
Zac


      reply	other threads:[~2015-01-30  7:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17 10:45 [gentoo-portage-dev] [PATCH] Default MAKEOPTS to -j(ncpus+1) when unset Michał Górny
2015-01-18  4:22 ` Zac Medico
2015-01-18  4:48   ` Zac Medico
2015-01-18  5:10     ` Tim Harder
2015-01-18  9:30     ` Michał Górny
2015-01-18 10:38     ` [gentoo-portage-dev] [PATCH v2] " Michał Górny
2015-01-18 16:58       ` Brian Dolbec
2015-01-29  3:06         ` Rick "Zero_Chaos" Farina
2015-01-30  7:05           ` Zac Medico [this message]

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=54CB2D3B.7050202@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@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