From: Simon Tournier <zimon.toutoune@gmail.com>
To: Vagrant Cascadian <vagrant@debian.org>,
Adam Faiz <adam.faiz@disroot.org>,
atai@atai.org
Cc: help-guix@gnu.org
Subject: Re: guix package build: can distcc be used?
Date: Mon, 09 Jan 2023 12:16:04 +0100 [thread overview]
Message-ID: <87a62syn4b.fsf@gmail.com> (raw)
In-Reply-To: <87a62vjy82.fsf@yucca>
Hi,
On ven., 06 janv. 2023 at 10:48, Vagrant Cascadian <vagrant@debian.org> wrote:
> I believe distcc would allow sending the workload of individual parts of
> a single package to multiple machines, so a bit finer grained than guix
> offload, which can only send a single package (or more accurately,
> derivation?) to each of the offloading machines, if I understand
> correctly.
Well, I would be interested to see charts comparing the overall
compilation time versus the number of files vs the number of remote
workers. Especially for various network connection links between the
client and the volunteer machines versus the performance of the hardware
storage. :-)
Speaking about improving some compilation performances, it could be nice
to have a kind of optional ccache [1]. For instance,
guix build foo --cache
edit foo-recipe
guix build foo --cache
would avoid to rebuild again and again the same parts.
Cheers,
simon
1: <https://ccache.dev/>
next prev parent reply other threads:[~2023-01-09 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 10:21 guix package build: can distcc be used? Adam Faiz
2023-01-06 16:12 ` zimoun
2023-01-06 18:48 ` Vagrant Cascadian
2023-01-09 11:16 ` Simon Tournier [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-24 9:33 Andy Tai
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a62syn4b.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=adam.faiz@disroot.org \
--cc=atai@atai.org \
--cc=help-guix@gnu.org \
--cc=vagrant@debian.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).