begin quote On Thu, 07 Aug 2003 11:21:25 +0200 Ole Langbehn <[EMAIL PROTECTED]> wrote:
> Hi, > > my home network consists of 1 Athlon XP 1800 and a P120 Server. > So I thought I would give distcc a try (maybe not a bad idea :). > > What I want is: Everything should be compiled on the fast Athlon > machine. I got this setup working, but I still have a few questions: > > first of all, the relevant parts of make.conf: > This is on the Athlon: > > #distcc > DISTCC_HOSTS="localhost" > DISTCC_VERBOSE=1 > MAKEOPTS="-j2" Why theese instead of FEATURES="distcc" ?? > CC="distcc" > CXX="distcc g++" > > This is on the P120: > > #distcc > DISTCC_HOSTS="athlon" > DISTCC_VERBOSE=1 > MAKEOPTS="-j4" > CC="distcc" > CXX="distcc g++" > > > With this setup, both machines compile on the athlon, but: > > - is there any way to shut down the distccd on the P120? When I did > this, I didn't get a connection to the Athlon anymore and everything > was compiled locally (on the P120) again... > - why is the CPU usage on the Athlon just at about 25% during compiles Try DISTCC_HOSTS="athlon/10 localhost" (first 10 jobs go to the athlon) > on the P120. I increased MAKEOPTS to -j4 to get slightly more CPU > usage, but am not sure this is the best way to get more performance. it is, the p120 has to do all the preprocessing, which is a lot in most c++ code. Try to even increase it further to -j6 (that should be enough to keep the athlon going at all times. track the athlons CPU usage for results) -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end
pgp00000.pgp
Description: PGP signature
