On Sun, Nov 27, 2011 at 5:07 PM, Mark Knecht <markkne...@gmail.com> wrote:
> On Sat, Nov 26, 2011 at 7:22 AM, Michael Mol <mike...@gmail.com> 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
>
> Good post Michael. Thanks.
>
> I want to verify that in make.conf this is indeed MAKEOPTS we are
> talking about and not EMERGE_DEFAULT_OPTS.
It'd be a combination of them.
EMERGE_DEFAULT_OPTS, for my 8-way system, would have been -j8 (I'll be
changing this to reflect portage's load-aware behavior).
MAKEOPTS would be -j16, -l10. (Which actually goes up to about 12 or
13 based on that N*1.6 behavior)
>
> Currently for my i7-980x (6 physical cores + hyper threading = 12
> logical cores) I have:
>
> MAKEOPTS="-j3"
> EMERGE_DEFAULT_OPTS="--with-bdeps y "
> PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"
>
> I generally keep -j small day-to-day to allow emerge to work more or
> less the background while I'm using the machine for other things. If I
> was going to do an emerge -e @world then in the past I'd push it up
> for 13. (N+1)
>
> I've not used the -l option but it sounds interesting. If I understand
> the then you're suggesting in /etc/make.conf
>
> MAKEOPTS="-j13 -l7"
>
> or something in that range for a full blown emerge -e @world?
Pretty much. Though I wouldn't do it just for @world. I'd leave it in
for all emerges.
--
:wq
