From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hoping someone can help explain distcc to me
Date: Sun, 21 Aug 2011 01:35:42 +0100 [thread overview]
Message-ID: <201108210135.43166.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <CAEH5T2M4b0b4jmwebYkodpDA59c7K2PEw=-jNk2OAhHMiPu3Fw@mail.gmail.com>
On Saturday 20 August 2011 23:56:08 Paul Hartman wrote:
> 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.
Your laptop isn't sending its compilation jobs to your desktop. Have you
used gkrellm or similar to check for network traffic?
I think I'd take a different approach, one that I dare say you can
anticipate. By all means take the advice you're about to be offered to get
distcc working, but why not create a chroot on your desktop, NFS export the
packages directory from the laptop to it and do the whole job there? Then
return to the laptop and emerge -k. It does need more keystrokes but it uses
far less CPU. You just need to copy /var/lib/portage/world, make.conf and
the /etc/portage tree to the chroot before you start.
I did once get distcc working, but as Neil has observed re Atoms, a lot of
work is still done before compilation is farmed out to the distcc server,
rather diluting the benefit of distributed compilation.
--
Rgds
Peter Linux Counter 5290, 1994-04-23
next prev parent reply other threads:[~2011-08-21 0:37 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 [this message]
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=201108210135.43166.peter@humphrey.ukfsn.org \
--to=peter@humphrey.ukfsn.org \
--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