mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Build speed ups
Date: Mon, 18 Sep 2017 15:43:07 +0200	[thread overview]
Message-ID: <20170918134306.xwykmdbd5myj7vre@falbala.home.lespocky.de> (raw)
In-Reply-To: <3066dd20-9749-e43a-b338-52a5f57a916d@erwinrol.com>


[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]

Hei hei,

On Mon, Sep 18, 2017 at 02:33:50PM +0200, Erwin Rol wrote:
> Distributed CC (distcc/icecc) seem a possibly to scale up things in
> smaller steps (ad cheap compile server one by one) Sadly I don't have
> any experience with it, but it is something I want to look into.

We use icecc here. Before using it, I had some doubts and thought it
would be complicated to setup, but it wasn't, also thanks to the
transparent integration in ptxdist. You can easily integrate
machines already running in your local network. Definitly something I
would give a try before buying new hardware.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6 ***

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-09-18 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 12:33 Erwin Rol
2017-09-18 13:43 ` Alexander Dahl [this message]
2017-09-18 17:14 ` Root
2017-09-19  4:45   ` Ulrich Ölmann
2017-09-19  6:42   ` Schenk, Gavin

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=20170918134306.xwykmdbd5myj7vre@falbala.home.lespocky.de \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /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