From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-user+bounces-131667-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1RUswf-0001sH-Qo
	for garchives@archives.gentoo.org; Mon, 28 Nov 2011 04:35:58 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 8CAA021C148;
	Mon, 28 Nov 2011 04:35:48 +0000 (UTC)
Received: from mail-bw0-f53.google.com (mail-bw0-f53.google.com [209.85.214.53])
	by pigeon.gentoo.org (Postfix) with ESMTP id E3C4321C149
	for <gentoo-user@lists.gentoo.org>; Mon, 28 Nov 2011 04:34:15 +0000 (UTC)
Received: by bkaq10 with SMTP id q10so9419038bka.40
        for <gentoo-user@lists.gentoo.org>; Sun, 27 Nov 2011 20:34:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=T6xA37Nw6rbWymgytMVvZSzkWnLR2eCaZod5HfSUXzg=;
        b=Jf+pyHYyIedRM/2k8Ze4ZjjNvS/w6rBvTY8Mb5SL6xfm/Hqc71wLvkaKU7qn9L2qU7
         eYzMmfmUTIbjrzPADlphF7JZUIu5Ke6GPtq8l9rxVVgGygKbKegXqQqTex7uDe4Q6A1u
         iJQKaCUn7bR14sYQgzMZSxWWPD6O6wneBFjMU=
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.204.13.68 with SMTP id b4mr43055096bka.32.1322454855060; Sun,
 27 Nov 2011 20:34:15 -0800 (PST)
Received: by 10.204.14.7 with HTTP; Sun, 27 Nov 2011 20:34:14 -0800 (PST)
In-Reply-To: <CAA2qdGU-qnp7Agv3Ha5L=YLotHD2MxfzBoXPPDTLYuxaQgBU+A@mail.gmail.com>
References: <CA+czFiB4pSTcVTgAbRnL6AUgGoE9E7gsg-1O0LgfU4FVF_DB+Q@mail.gmail.com>
	<201111270927.57294.michaelkintzios@gmail.com>
	<CA+czFiBAR2_j1vETXGZk6SL9XK9w=doe4orU+bLeZbXHXBUqPg@mail.gmail.com>
	<CAA2qdGWwuHUUd7ZkbBOwJxx8Ax88xfAptASgvbFtNa0YMqe6bQ@mail.gmail.com>
	<20111127232108.08cbacfd@digimed.co.uk>
	<CAA2qdGU-qnp7Agv3Ha5L=YLotHD2MxfzBoXPPDTLYuxaQgBU+A@mail.gmail.com>
Date: Sun, 27 Nov 2011 23:34:14 -0500
Message-ID: <CA+czFiDNeBusc4izgsvdBFXC6e+JQ-Ax6K+2xdhrMiJ20A34jg@mail.gmail.com>
Subject: Re: [gentoo-user] emerge -j, make -j and make -l
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: 67317517-db32-43ec-b52a-d942376c47fb
X-Archives-Hash: 9b296f98847d1239868d20b7344ed112

On Sun, Nov 27, 2011 at 7:54 PM, Pandu Poluan <pandu@poluan.info> wrote:
>
> On Nov 28, 2011 6:24 AM, "Neil Bothwick" <neil@digimed.co.uk> wrote:
>>
>> On Mon, 28 Nov 2011 00:56:17 +0700, Pandu Poluan wrote:
>>
>> > I don't know where the 'blame' lies, but I've found myself
>> > standardizing on MAKEOPTS=-j3, and PORTAGE_DEFAULT_OPTS="--jobs
>> > --load-average=<1.6*num_of_vCPU>"
>> >
>> > (Yes, no explicit number of jobs. The newer portages are smart enough to
>> > keep starting new jobs until the load number is reached)
>>
>> The problem I found with that is the ebuilds load the system lightly to
>> start with, before they enter the compile phase, to portage starts dozens
>> of parallel ebuilds, then the system gets completely bogged down when
>> they start compiling.
>>
>
> Yes, sometimes that would happen if at the beginning there are network-bound
> ebuilds all downloading their respective distfiles. The load stays low until
> they all start ./configure-ing roughly at the same time. Then all hell
> breaks loose.
>
> I successfully mitigate such "load-explosion" by doing a --fetchonly step
> first, and keeping MAKEOPTS at low -j (which, in my case, is actually
> required).
>
> Just to add more info: I use USE=graphite (with some CFLAGS, uh,
> 'enhancements') with gcc-4.5.3. IIRC, I could push MAKEOPTS up to -j5 (and
> even more, but I ran out of cores) when I was still using gcc-4.4.x and no
> USE=graphite.
>
> Won't file a bug report, though. I have a feeling that my bug report re:
> emerge failure will be marked WONTFIX thanks to the 'ricer special' CFLAGS

As I noted, "-l" in MAKEOPTS takes care of the load explosion very nicely.
-- 
:wq