Walter Dnes wrote:
> On Sat, Oct 14, 2017 at 06:25:35AM -0500, Dale wrote
>
>> Some of my make.conf entries. You may not need all of these so edit out
>> what you don't want or change values if you need to. I have a four core
>> CPU.
>>
>> FEATURES="-usersync -userpriv -usersandbox buildpkg sandbox parallel-fetch"
>>
>> MAKEOPTS="-j5"
> There is some controversy over setting MAKEOPTS=${number of threads}
> possibly being better than MAKEOPTS=${number of threads} + 1
> https://blogs.gentoo.org/ago/2013/01/14/makeopts-jcore-1-is-not-the-best-optimization/
>
I tried different settings before that one and settled on the one that
works best. It may not work on someone else's system but it does fine
here. One thing about most of my settings, they've been tested pretty
well and work well on this system at least.
Since I have a four core system, I usually set everything to number of
cores plus one which should lead to a always busy CPU. So far, it has
worked out that way for the most part. If I had enough memory, I might
could up that but it could lead to another problem I had before lowering
it to that number. Compiles that fail. It's been a while but at one
point, some packages had to have -j 1 to compile. That is rare nowadays
I guess but since the settings I have works for me, I'll likely leave
them like they are.
The one thing I did have to change recently, not compiling some large
packages on tmpfs. If it was just one package I have enough memory.
However, sometimes it would be two and sometimes even three that were
large. The main culprits were Seamonkey, Firefox and Libreoffice. I
think I added a couple other large ones in just to be sure but other
than that, these settings have been around for a good long while.
I might add, I've read that blog before. I also read the comments where
others had different results and pointed out some issues with the blog
points. The blogger used kdelibs as a test case. Thing is, I compile
more than just kdelibs here. Most of the time I start my emerges before
I go to sleep. I put Gkrellm where I can see it and I watch what the
CPUs are doing. Generally speaking, the CPU cores stay busy the whole
time. There are a few times that it is not at 100% but generally it
is. If anything, since it does have times where it isn't at 100%, I may
need to up that number by one to see if that keeps it more busy. Thing
is, in the past, it didn't help any.
Thanks for the info.
Dale
:-) :-)
