Am 29.11.2011 16:39, schrieb Neil Bothwick: > The trouble with --load-average in emerge is that it is only > checked as each ebuild is about to start, so you get the "load > explosion" mentioned previously when many ebuilds start and once > and then get into their compile phases. I'm using --jobs, with no > value, in EMERGE_DEFAULT_OPTS and the -l10 for make seems to take > care of the load very nicely (sorry about the pun there).
ok with me ;-) I now use: EMERGE_DEFAULT_OPTS="--jobs" MAKEOPTS="-j18 -l10" and that is rather fast, yes .... thanks ... I start to "feel" the potential of that new CPU, yes. Stefan