From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Project Glentoo: Status Report #4
Date: Fri, 15 Jul 2011 09:53:18 -0500 [thread overview]
Message-ID: <20110715145318.GA2828@comet.mayo.edu> (raw)
In-Reply-To: <CAGfcS_=YSThGqxLmE56w+HH4bScxRSZQm7aA8qDPCxtio_h91Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
On 10:25 Fri 15 Jul , Rich Freeman wrote:
> On Sun, Jun 19, 2011 at 7:42 PM, Robert Seaton <seatonr@dupage.edu> wrote:
> > On Wednesday, I spent some time trying to get distcc working on an
> > Amazon EC2 high-compute instance to speed up generation of the process
> > of building a liveCD image, seeing as it takes quite some time to
> > generate a fresh image on my aging core2duo. I still haven't managed
> > to get that working, but it's something I plan to continue to look
> > into during the upcoming week.
>
> Out of curiosity - did you ever get this working in any practical way?
> I've found that DistCC to a remote server from a slower host hasn't
> worked all that well. In order to make up for network latency you
> need to run VERY parallel builds (-j15/etc), and the problem is that
> there is no way to tell make to do that just for files that use gcc.
> The result is that as soon as you hit a package that uses quite a bit
> of java/python/bash/etc you end up running at -j15 on your local
> system and it just kills you - especially java.
There's a nice option -l (load average) that blocks new jobs from
starting if the load is too high.
--
Thanks,
Donnie
Donnie Berkholz
Admin, Summer of Code
Gentoo Linux and X.Org
Blog: http://dberkholz.com
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-07-15 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 23:42 [gentoo-soc] Project Glentoo: Status Report #4 Robert Seaton
2011-07-15 14:25 ` Rich Freeman
2011-07-15 14:53 ` Donnie Berkholz [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=20110715145318.GA2828@comet.mayo.edu \
--to=dberkholz@gentoo.org \
--cc=gentoo-soc@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