unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: gwl-devel@gnu.org
Subject: How do I support building a guix package over multiple machines in a cloud environment?
Date: Mon, 2 Dec 2019 12:36:30 -0500	[thread overview]
Message-ID: <CAFkJGRcHeL7DqPfR9nGXGyV_Q1bVURmYJ9LOLD8eObW-pdJz9g@mail.gmail.com> (raw)

Hello all,

Simon directed me from help-guix to wake up this list.  I have a use
case or a colleague to articulate their work as a guix package.  I'm
still very new, and would like to use this as a learning opportunity.
He uses it as a bioinformatics workflow to generate some analysis.  It
typically runs in 6 threads, 42GB peak memory, 100GB of on disk files,
and is currently using nextflow.  This seems like a perfect use case
to try out doing more with guix/gwl.  His workflow is more analogous
to software packaging  that a dumb software pipeline or even a re-run
optimized bioinformatics pipeline.

Is this kind of use case supported?  If so, how so?  Is nextflow not
practical to keep?  Please, someone catch me up here so I can start to
write code to help him out.  If this goes well, my company could
integrate for gwl/guix in our work, which would be amazing.

             reply	other threads:[~2019-12-02 17:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 17:36 Josh Marshall [this message]
2019-12-02 19:00 ` How do I support building a guix package over multiple machines in a cloud environment? zimoun
2019-12-02 20:02   ` pjotr.public12
2019-12-02 20:16     ` Josh Marshall
2019-12-02 21:00       ` zimoun
2019-12-02 20:03   ` Josh Marshall
2019-12-02 20:59     ` zimoun
2019-12-02 23:39 ` Ricardo Wurmus
2019-12-03  3:00   ` Josh Marshall
2019-12-03 11:03   ` zimoun
2019-12-03 13:47     ` Pjotr Prins

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://www.guixwl.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFkJGRcHeL7DqPfR9nGXGyV_Q1bVURmYJ9LOLD8eObW-pdJz9g@mail.gmail.com \
    --to=joshua.r.marshall.1991@gmail.com \
    --cc=gwl-devel@gnu.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).