So I'm running the 2.2-rcs and have been seeing blogs about the new
parallel merge capacities... Having a dual-dual-core Opteron and having
run multiple merges manually for some time, this is VERY welcome news.
=8^)
So after upgrading to -rc3 I set EMERGE_DEFAULT_OPTS to include
--jobs=10
Duncan wrote:
--jobs=10 --keep-going --load-average=15
For a dual-dual-core setup, a load average of 4.0 is fully loaded. Anything
higher than that and you're just causing jobs to queue up unnecessarily and your
system to thrash.
have MAKEOPTS=-j -l20 so it's not going to be low all the
Andrew Gaffney [EMAIL PROTECTED] posted [EMAIL PROTECTED],
excerpted below, on Sat, 26 Jul 2008 16:56:20 -0500:
Duncan wrote:
--jobs=10 --keep-going --load-average=15
For a dual-dual-core setup, a load average of 4.0 is fully loaded.
Anything higher than that and you're just causing jobs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
For the first 100 or so packages, it worked quite well. However, about
there, maybe package 120 or so, so about 20% of the way thru, it reverted
to doing them one-at-a-time again. I'm now on package #279 and it's
still doing
On Sat, 26 Jul 2008 16:56:20 -0500
Andrew Gaffney [EMAIL PROTECTED] wrote:
Duncan wrote:
--jobs=10 --keep-going --load-average=15
For a dual-dual-core setup, a load average of 4.0 is fully loaded.
Only in ideal cases, when you have long-running processes
hammering the cpu and little or no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ali Polatel wrote:
Thanks for the comments.
I haven't been able to finish reviewing your patch yet but I just
want you to know that it's still in my queue.
Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
