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] Re: Hoping someone can help explain distcc to me
Date: Mon, 22 Aug 2011 14:47:29 -0500	[thread overview]
Message-ID: <CAEH5T2P5UvkH875=4pmS5yk1epVEAVDtpYOhs3ObWzebhXR1+A@mail.gmail.com> (raw)
In-Reply-To: <CAEH5T2M4b0b4jmwebYkodpDA59c7K2PEw=-jNk2OAhHMiPu3Fw@mail.gmail.com>

On Sat, Aug 20, 2011 at 5:56 PM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
>
> 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.

Thanks to all who replied for your suggestions and info! After
experimenting with various combinations of settings it seems to be
working now. I think I was too aggressive with the number of parallel
make jobs, the laptop just couldn't coordinate that many. I also
stopped distccd on the laptop, in case it was picking up jobs
unintentionally.

Here's the results, a real-life test with ImageMagick 6.7.1.0. The
machines were idle, files were already downloaded, and I don't use
ccache, so it should be actual compile time comparison only:

Normal emerge on laptop, no parallel jobs in MAKEOPTS, no distcc:
merge time: 8 minutes and 27 seconds.

With -j3 in MAKEOPTS, using distcc:
merge time: 4 minutes and 40 seconds.

Great!

Of course, on the desktop it only takes 1 minutes 17 seconds, but an
almost 50% reduction in emerge time on the laptop is still great to
see.



      parent reply	other threads:[~2011-08-22 19:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20 22:56 [gentoo-user] Hoping someone can help explain distcc to me Paul Hartman
2011-08-21  0:35 ` 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 ` Paul Hartman [this message]

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='CAEH5T2P5UvkH875=4pmS5yk1epVEAVDtpYOhs3ObWzebhXR1+A@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