public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Hoping someone can help explain distcc to me
Date: Sat, 20 Aug 2011 17:56:08 -0500	[thread overview]
Message-ID: <CAEH5T2M4b0b4jmwebYkodpDA59c7K2PEw=-jNk2OAhHMiPu3Fw@mail.gmail.com> (raw)

Hi,

I have a fast desktop computer and a slow laptop. Both are ~amd64
Gentoo. After some of the recent discussions about Gentoo on slow
devices, I thought I'd dust off the laptop and try to bring it up to
date.

I'd like to use distcc to make the desktop do all the compiling during
emerges. I've never been able to get distcc working properly, or, at
least, I've never been able to get it working to the point where using
distcc is any faster than not using it at all.

Desktop: 192.168.0.100
Laptop: 192.168.0.107

My goal is to just don't use the laptop at all. Do all compiling on
the desktop. So far, while it appears to be working (some things are
being compiled on the desktop, a very insignificant amount -- CPU
usage on the desktop is basically 0% during emerges on the laptop),
compile times are no better than just compiling everything on the
laptop. The laptop still has 100% CPU activity during emerges. I
realize the laptop is still going to do work during emerges, but
thought at least distcc might be able to help offload most of the
heavy part (the compiling).

Both machines contain "distcc" in FEATURES. It's not using
-march=native. I've tried various -jN values with no real difference
in performance.

On the desktop, /etc/conf.d/distcc contains (among other things):
DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.0.0/24"
DISTCCD_OPTS="${DISTCCD_OPTS} --listen 192.168.0.100"

And /etc/distccd/hosts contains:
192.168.0.0/24

On the laptop, /etc/conf.d/distcc contains (among other things):
DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.0.0/24"
DISTCCD_OPTS="${DISTCCD_OPTS} --listen 192.168.0.107"

And /etc/distccd/hosts contains:
192.168.0.100

Does anyone know any tricks or can tell me if I'm doing something
wrong? How much of a speed-up should I realistically expect? Should
distcc be able to exploit the fast machine to the fullest of its
abilities?

Thanks



             reply	other threads:[~2011-08-20 22:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20 22:56 Paul Hartman [this message]
2011-08-21  0:35 ` [gentoo-user] Hoping someone can help explain distcc to me Peter Humphrey
2011-08-21  1:08   ` Paul Hartman
2011-08-21  1:58     ` Peter Humphrey
2011-08-21  2:46       ` Dale
2011-08-21  3:04         ` Matthew Finkel
2011-08-21  9:41           ` Peter Humphrey
2011-08-21 13:53             ` Joost Roeleveld
2011-08-21 16:27               ` Peter Humphrey
2011-08-21 17:42               ` Neil Bothwick
2011-08-24 11:04             ` Dale
2011-08-21  1:34 ` victor romanchuk
2011-08-21 10:38   ` Alex Schuster
2011-08-21 14:39     ` victor romanchuk
2011-08-22 20:41       ` Alex Schuster
2011-08-22 22:36         ` Bill Longman
2011-08-22 22:41         ` Bill Longman
2011-08-22 19:47 ` [gentoo-user] " Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEH5T2M4b0b4jmwebYkodpDA59c7K2PEw=-jNk2OAhHMiPu3Fw@mail.gmail.com' \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox