Please use the list. On 16 Nov 2003, AthlonRob <[EMAIL PROTECTED]> wrote: > On Sun, 2003-11-16 at 17:52, Martin Pool wrote: > > What exactly is the problem here? Those logs show that things are > > successfully being compiled on 192.168.1.2... > > The logs are lying...
Uh, right. > Either that, or things have completely changed with distcc in the last > year. > > See, I'm compiling some monster things... things like the kernel... and > the CPU on the only host listed in DISTCC_HOSTS is sitting mostly idle, > spiking up to 25% for a few seconds, at max. > > I just upped it to -j10 with one host and it started getting a little > bit higher. Maybe it's just network saturation... I understand there's > some LZO compression enablable somewhere... I'll check that out? I'm on > a wifi link. > > A year ago, when I'd run distcc, I was able to keep three computers > crunching at 75-95% utilization without any issues... Over wifi? I'd be pretty surprised if you could keep three machines busy over a (less than) 5Mbps link, unless you were building super hairy C++ code. Yes, adding ",lzo" to the hosts will turn on compression and probably speed things up. -- Martin linux.conf.au -- Adelaide, January 2004 __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc