1 |
On Sun, Nov 27, 2011 at 5:07 PM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> On Sat, Nov 26, 2011 at 7:22 AM, Michael Mol <mikemol@×××××.com> wrote: |
3 |
>> I just wanted to share an experience I had today with optimizing parallel |
4 |
>> builds after discovering "-l" for Make... |
5 |
>> |
6 |
>> I've got a little more tweaking I still want to do, but this is pretty |
7 |
>> awesome... |
8 |
>> |
9 |
>> http://funnybutnot.wordpress.com/2011/11/26/optimizing-parallel-builds/ |
10 |
>> |
11 |
>> ZZ |
12 |
> |
13 |
> Good post Michael. Thanks. |
14 |
> |
15 |
> I want to verify that in make.conf this is indeed MAKEOPTS we are |
16 |
> talking about and not EMERGE_DEFAULT_OPTS. |
17 |
|
18 |
It'd be a combination of them. |
19 |
|
20 |
EMERGE_DEFAULT_OPTS, for my 8-way system, would have been -j8 (I'll be |
21 |
changing this to reflect portage's load-aware behavior). |
22 |
|
23 |
MAKEOPTS would be -j16, -l10. (Which actually goes up to about 12 or |
24 |
13 based on that N*1.6 behavior) |
25 |
|
26 |
> |
27 |
> Currently for my i7-980x (6 physical cores + hyper threading = 12 |
28 |
> logical cores) I have: |
29 |
> |
30 |
> MAKEOPTS="-j3" |
31 |
> EMERGE_DEFAULT_OPTS="--with-bdeps y " |
32 |
> PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}" |
33 |
> |
34 |
> I generally keep -j small day-to-day to allow emerge to work more or |
35 |
> less the background while I'm using the machine for other things. If I |
36 |
> was going to do an emerge -e @world then in the past I'd push it up |
37 |
> for 13. (N+1) |
38 |
> |
39 |
> I've not used the -l option but it sounds interesting. If I understand |
40 |
> the then you're suggesting in /etc/make.conf |
41 |
> |
42 |
> MAKEOPTS="-j13 -l7" |
43 |
> |
44 |
> or something in that range for a full blown emerge -e @world? |
45 |
|
46 |
Pretty much. Though I wouldn't do it just for @world. I'd leave it in |
47 |
for all emerges. |
48 |
|
49 |
-- |
50 |
:wq |