From: Ricardo Wurmus <rekado@elephly.net>
To: Phil <phil@beadling.co.uk>
Cc: help-guix@gnu.org
Subject: Re: Guix for Corporate "Batch Jobs"?
Date: Wed, 09 Mar 2022 09:20:51 +0100 [thread overview]
Message-ID: <878rtjwn4n.fsf@elephly.net> (raw)
In-Reply-To: <87sfrs2ftx.fsf@beadling.co.uk>
Phil <phil@beadling.co.uk> writes:
> I don't think GWL can memoize
> different processes in a workflow tho - so running a workflow several
> times results in all workflow processes being run, as far as I know.
By default GWL caches outputs that have already been computed.
Currently there’s only one way to skip computation and that is through
files. When a computation results in a file the output is cached; if
the output exists already then the computation is not re-rerun unless
explicitly requested.
(The GWL needs even more caching to avoid recomputing build scripts, but
that’s a separate issue.)
--
Ricardo
next prev parent reply other threads:[~2022-03-09 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 21:16 Guix for Corporate "Batch Jobs"? Yasuaki Kudo
2022-03-08 23:18 ` Phil
2022-03-09 8:20 ` Ricardo Wurmus [this message]
2022-03-09 8:49 ` Yasuaki Kudo
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=878rtjwn4n.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=phil@beadling.co.uk \
/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).