<PurpleSym>I’m nearly done with the automated CRAN channel and performance with an additional 17000 packages is pretty brutal. `guix pull` takes five minutes to build the channel’s derivation, `guix search` for a nonexistent package goes up from .6s to 1s, `guix show` is up from .1s to .13s
<PurpleSym>Hopefully the `guix pull` performance hit can be avoided via substitutes.
<civodul>did you set up machinery to update the channel automatically?
<civodul>if you want i can have it built on guix.bordeaux.inria.fr
<PurpleSym>No automated updates yet, no. That’s up next on my list.
<PurpleSym>Sure, if you have the capacity to build 17k packages, go ahead. I’m building them locally right now, because I’m curious how many succeed. I’ll also build them on substitutes.guix.psychnotebook.org, because that’s where I need them.
<PurpleSym>Hopefully this entire endeavor will silence those who claim Guix does not have enough packages 😉
<efraim>PurpleSym: is it better if the packages are split haphazardly across different modules? I found I had terrible performance when I tried to make a channel with ~8000 packages in one file
<PurpleSym>efraim: I tried a single file, which was slightly slower (maybe module compilation is accidentally quadradic somewhere?) and one file per package, which caused Guile to implode. So, this is kind of the middle ground.
<PurpleSym>(And single file means: 17k packages in a single file.)