public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Pool <mbp@samba.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Parallel make
Date: Fri, 16 May 2003 04:44:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705889@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705774@msgid-missing>

On 15 May 2003, Stephane Eranian <eranian@hpl.hp.com> wrote:

> Yes, distcc is really nice. I have been using it for a month or so
> for my kernel compiles using a cluster of Itanium 2 machines. What
> I like is that it is really easy to setup. The danger with the
> approach is that you can easily overload your local (master) host.

It can work well to use -l as well as -j, to put an upper limit on the
load on the master host.  If you have 2 local CPUs and 8 altogether
then perhaps.

  make -l4 -j10

That ought to make concurrency ramp down as it gets into the linking
phase. 

I ought to add that to the manual/faq.

> As for kernel compiles for 2.5, there are a lot of ld steps
> which are still all done on the master node.  Besides that you
> can really feel the speed difference. I need to take a look at ccache
> now that you mention it.
> 
> Very cool. 

Thanks, I'm glad you like it.

-- 
Martin 


      parent reply	other threads:[~2003-05-16  4:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  3:38 [Linux-ia64] Parallel make Ian Wienand
2003-05-14  4:29 ` Ian Wienand
2003-05-14  4:44 ` David Mosberger
2003-05-14  7:27 ` Eric Piel
2003-05-14  8:03 ` David Mosberger
2003-05-14  8:42 ` Eric Piel
2003-05-14 17:48 ` Sam Ravnborg
2003-05-14 18:42 ` David Mosberger
2003-05-14 23:00 ` David Mosberger
2003-05-14 23:59 ` Martin Pool
2003-05-15  0:49 ` Ian Wienand
2003-05-15  1:10 ` David Mosberger
2003-05-15 16:46 ` Stephane Eranian
2003-05-15 17:38 ` Grant Grundler
2003-05-16  4:44 ` Martin Pool [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=marc-linux-ia64-105590723705889@msgid-missing \
    --to=mbp@samba.org \
    --cc=linux-ia64@vger.kernel.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