On Fri, Dec 9, 2011 at 11:35 PM, Michael Mol <mike...@gmail.com> wrote: > Quick update...I now have two of these things set up in a distcc cluster > with my Phenom 9650. ~530 packages in 228m 34s. There's an even larger > initial explosion of parallel emerge jobs, but it spreads out very > nicely...I may have to increase the -j parameter in MAKEOPTS. I'm also not > certain if distcc is properly deferring jobs to the local host, but I got > the impression the local machine was getting a doubled workload when I had > 127.0.0.1 in/etc/distccd/hosts. > > ZZ
Another update: I've been playing with distcc a fair amount. One of the problems I discovered is that distcc doesn't get leveraged all that much if you have something like: MAKEOPTS="-j16 -l8" EMERGE_DEFAULT_OPTS="--jobs --load-average=8" It seems that "./configure" scripts and other non-distributable load pumps up the master system's load average enough that distributable jobs don't get spawned. (And why should they? Make doesn't know that a job will get shuttled off to another system.) After getting Gentoo set up on my new dual-core i3 laptop, I discovered that it seemed to emerge faster than my 8-core boxes with MAKEOPS="-j16 -l4" EMERGE_DEFAULT_OPTS="-jobs --load-average=3" ...It was doing a good job of shuffling jobs off to the two 8-way machines. (The new laptop only has 100Mbit ethernet, so I've also enabled LZO for distcc) With that in mind, I'm going to be trying these settings on the 8-way machines: MAKEOPTS="-j32 -l16" EMERGE_DEFAULT_OPTS="--jobs --load-average=12" -- :wq
