From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Lightning talk at IPFS camp
Date: Mon, 01 Jul 2019 12:16:08 +0200 [thread overview]
Message-ID: <8736jqqcuv.fsf@gnu.org> (raw)
In-Reply-To: <87ef3eznuv.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Fri, 28 Jun 2019 00:04:40 +0200")
Hi,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> All good, I had a look at the discussion and I'll study the patch a bit
> more.
>
> Today I learnt that Nix also had tried the same thing some 2 years
> back. And they ran into scalability issues. Maybe we should ask the
> Nix folks. Does anyone know more details about this?
I remember discussing it with lewo of NixOS at the R-B Summit. My
recollection is that the prototype that had been developed was using
IPFS in a brute-force fashion, something like directly storing nars and
narinfos, as opposed to storing individual files from the store using
“UnixFS” & co. I can no longer find the code that we looked at though,
that was somewhere on GitHub.
Note also that inserting files in IPFS takes quite a bit of CPU time and
memory, so that also could take ‘guix publish’ busy.
Ludo’.
prev parent reply other threads:[~2019-07-01 10:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 7:07 Lightning talk at IPFS camp Pierre Neidhardt
2019-05-31 22:10 ` Ludovic Courtès
2019-06-03 15:15 ` Konrad Hinsen
2019-06-03 16:19 ` Pronaip
2019-06-03 18:53 ` Konrad Hinsen
2019-06-06 8:13 ` Pierre Neidhardt
2019-06-06 12:15 ` Konrad Hinsen
2019-06-06 12:36 ` Pierre Neidhardt
2019-06-06 16:53 ` Konrad Hinsen
2019-06-07 12:39 ` Ludovic Courtès
2019-06-07 13:48 ` Konrad Hinsen
2019-06-07 20:10 ` Ludovic Courtès
2019-06-07 12:41 ` Ludovic Courtès
2019-06-07 13:45 ` Konrad Hinsen
2019-06-13 21:38 ` ng0
2019-06-24 20:37 ` Pierre Neidhardt
2019-06-26 12:19 ` Pierre Neidhardt
2019-06-27 14:53 ` Ludovic Courtès
2019-06-27 22:04 ` Pierre Neidhardt
2019-07-01 10:16 ` Ludovic Courtès [this message]
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=8736jqqcuv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).