all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Use guix to distribute data & reproducible (data) science
Date: Mon, 19 Feb 2018 00:42:01 +0100	[thread overview]
Message-ID: <87r2phhnli.fsf@gnu.org> (raw)
In-Reply-To: <24274adb01ba9c928a4701054b686a4a@hypermove.net> (Amirouche Boubekki's message of "Fri, 16 Feb 2018 17:43:40 +0100")

Hi Amirouche,

Amirouche Boubekki <amirouche@hypermove.net> skribis:

> On 2018-02-09 18:13, ludovic.courtes@inria.fr wrote:
>> Hi!
>>
>> Amirouche Boubekki <amirouche@hypermove.net> skribis:
>>
>>> tl;dr: Distribution of data and software seems similar.
>>>        Data is more and more important in software and reproducible
>>>        science. Data science ecosystem lakes resources sharing.
>>>        I think guix can help.
>>
>> I think some of us especially Guix-HPC folks are convinced about the
>> usefulness of Guix as one of the tools in the reproducible science
>> toolchain (that was one of the themes of my FOSDEM talk).  :-)
>>
>> Now, whether Guix is the right tool to distribute data, I don’t know.
>> Distributing large amounts of data is a job in itself, and the store
>> isn’t designed for that.  It could quickly become a bottleneck.
>
> What does it mean technically that the store “isn't designed for that”?

There are several potential issues.  One is GC: how convenient is it to
have big datasets subject to GC?  Another one is I/O bottleneck: when
adding a file to the store, you currently do an ‘add-to-store’ RPC to
the daemon, pass it the file name, which the daemon then reads entirely
to compute its content hash; could be an issue with big datasets.

HTH,
Ludo’.

  parent reply	other threads:[~2018-02-18 23:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 16:43 Use guix to distribute data & reproducible (data) science Amirouche Boubekki
2018-02-17 22:21 ` Roel Janssen
2018-02-18 23:42 ` Ludovic Courtès [this message]
2018-02-19  7:57 ` Ricardo Wurmus
  -- strict thread matches above, loose matches on Subject: below --
2018-02-09 16:32 Amirouche Boubekki
2018-02-09 17:13 ` Ludovic Courtès
2018-02-09 17:48   ` zimoun
2018-02-09 19:15   ` Konrad Hinsen
2018-02-09 23:01     ` zimoun
2018-02-09 23:17       ` Ricardo Wurmus
2018-02-12 11:46       ` Konrad Hinsen
2018-02-10  9:51     ` Amirouche Boubekki
2018-02-10 11:28       ` zimoun
2018-02-14 13:06     ` Ludovic Courtès
2018-02-15 17:10       ` zimoun
2018-02-16  9:28         ` Konrad Hinsen
2018-02-16 14:33           ` myglc2
2018-02-16 15:20             ` Konrad Hinsen
2018-02-16 12:41         ` Amirouche Boubekki

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=87r2phhnli.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=amirouche@hypermove.net \
    --cc=guix-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.
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.