1 |
From: Raffaele Belardi <raffaele.belardi@××.com> |
2 |
Sent: Wednesday, November 22, 2017 8:12 AM |
3 |
To: gentoo-user@l.g.o |
4 |
Subject: Re: [gentoo-user] is multi-core really worth it? |
5 |
|
6 |
Jeremi Piotrowski wrote: |
7 |
> That being said: if you do a world rebuild you will have lots of packages |
8 |
> that spend ~40 seconds doing their autoconf run, only to build 2-3 sources |
9 |
> files. On an 8-core machine at work, I get good results using parallel |
10 |
> emerge jobs (emerge -jX). For your 6-core AMD CPU (assuming it actually |
11 |
> has 12 threads) I'd start with 'emerge -j3' and MAKEOPTS='-j12 -l16'. |
12 |
> That should get you a nice speedup, but may require a bit more ram. |
13 |
|
14 |
emerge -j3 is something I did not think of, I'll try it. But won't that break portage's |
15 |
carefully crafted package dependencies? I suppose you could get occasional build failures? |
16 |
|
17 |
I'm using MAKEOPTS=-j7, I thought 2 threads per CPU (hyperthreading?) was an Intel thing only. |
18 |
|
19 |
raffaele |
20 |
|
21 |
|
22 |
There are alot of good tweaks to get by long configure sections, I have an octa core, so for normal updates I use - |
23 |
MAKEOPTS="-j8" # for 8 cores being used per package |
24 |
EMERGE_DEFAULT_OPTS="--jobs 2 --load-average 4" # only starts 2nd job if load average is low. |
25 |
|
26 |
You won't get build failures or dependency problems, portage is built to handle emerging multiple packages that do not depend on each other simultaneously. |
27 |
it will not ever build a dependency and the main program at the same time. |
28 |
|
29 |
PORTAGE_NICENESS="19" # best setting ever, I do some gaming while updating, you mainly only notice install phase if your are loading while the disk queue is full of writes. |