From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: support for containers
Date: Wed, 30 Jan 2019 11:17:02 +0100 [thread overview]
Message-ID: <CAJ3okZ0QGwo6dzdYwEpMBauYN2vYgFMuYMR2jAuk=nTGoLhkZg@mail.gmail.com> (raw)
In-Reply-To: <87womnnjg0.fsf@elephly.net>
Hi Ricardo,
On Wed, 30 Jan 2019 at 00:16, Ricardo Wurmus <rekado@elephly.net> wrote:
> Since we don’t hash the data (because it’s expensive) the scripts are
> “proxies” for the data files. We compute the hashes over the dependent
> scripts and assume that this is enough to decide whether to recompute
> data files or to serve them from the cache/store.
Just to be sure to well understand your point, let pick the simple
example from genomics pipeline:
FASTQ -align-> BAM -variant-> VCF
So, you intend to hash:
- the data FASTQ
- the scripts align and variant
Or only the scripts containing reference to inputs (here FASTQ), where
the reference is a location fixed by the user.
Well, hashing the scripts and assuming they "mirror" the data files
appear to me an efficient design for the CAS.
--
simon
next prev parent reply other threads:[~2019-01-30 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 23:03 support for containers Ricardo Wurmus
2019-01-29 9:38 ` Ricardo Wurmus
2019-01-29 10:39 ` zimoun
2019-01-29 11:46 ` Ricardo Wurmus
2019-01-29 14:29 ` zimoun
2019-01-29 17:19 ` Ricardo Wurmus
2019-01-29 21:52 ` zimoun
2019-01-29 23:16 ` Ricardo Wurmus
2019-01-30 10:17 ` zimoun [this message]
2019-01-30 12:46 ` Ricardo Wurmus
2019-01-29 10:22 ` zimoun
2019-01-29 11:44 ` Ricardo Wurmus
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='CAJ3okZ0QGwo6dzdYwEpMBauYN2vYgFMuYMR2jAuk=nTGoLhkZg@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.