-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan schrieb:
> Also, a little monitoring utility that could be run in another terminal
> and just list and update all the currently merging packages, and any that
> had failed to merge, so I could take a look at them while the system is
> still w
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 lit
-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
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 al
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 --
