<vagrantc>so... how much space does /gnu/store "typically" take up over time ? obviously, this varies greatly by user, but what would be a reasonable amount to host a public mirror/proxy? would 450GB be useful? or just a waste of time?
<OriansJ>janneke: well you know I'd change M1 to make it better for you but if life is easier for you to output M2-Planet, that is also an option if you wish to do that
<OriansJ>or if you wanted to be kinda crazy, you could output slow_lisp or M2-Moon (when I am done with it of course)
<brendyn>since a created my wifi network config in gnome, now that im in i3 it requires me to run polkit-gnome-authentication-agent-1 to edit that config, but not the one i created before i installed gnome. rather annoying
<brendyn>i swear im never touching gnome ever again
<mfzap>hi all... having trouble on aws ec2 nano and micro instances - guix pull seems to lack the memory to complete, I get out of memory errors... they are 0.5GB and 1GB respectively. Adding a GB of swap didn't help (cancels for extended silence). How much RAM does guix pull need? Can I reduce the requirement to make it work on these usefully small instances? thanks!
<lfam>mfzap: It should work with 1 GB RAM and 1 GB swap but, as you noticed, using swap will take a very long time.
<lfam>You can set the options --timeout and --max-silent-time to a high number to avoid timeout cancellations
<lfam>I recommend setting it to something like 12 hours. It shouldn't take that long but since you are sharing the underlying disk while using EC2 micro instances, it could potentially take forever if EC2s I/O sharing mechanism penalizes you for some reason
<lfam>I use Guix on a micro EC2 and that's what I do
<lfam>We know that these memory requirements are really too high, but it's taking a while to find and fix or workaround the bugs that cause such high memory consumption
<mfzap>ya that's an wise observation, eventually engineering it to run under 1GB would be a nice goal
<lfam>It's probably worth using an SSD for this use case (I'm still using spinning disks on EC2)
<lfam>It used to require much less memory with the previous version of the Guile compiler, but some optimizations in the new version ended up being more RAM-expensive than expected
<mfzap>oh, those opts can't be turned off? maybe that's a trade-off that some people would choose
<lfam>There is a package 'guile2.0-guix'. I haven't tried using it but it sounds like a version of Guix that uses the previous version of Guile
<lfam>(We should clarify what it is in the package description!)
<mfzap>if I get through the initial guix pull, are subsequent pulls "easier" or they all run the same way? sometimes the initial update of a system is heavier
<lfam>Currently each pull recompiles all of Guix (Guix itself, not all the packages), if I understand correctly
<lfam>People are working to fix the issues in Guile, and we are also doing some workarounds in Guix in the meantime. But still we need >1 GB RAM to do `guix pull`
<lfam>It's unfortunate considering that there is lots of interesting hardware with only 1 GB RAM
<mfzap>just tried an aws ec2 small, and it does a guix pull very well. ec2 micro and nano are the ones that struggle. would be nice to get micro to work over time. nano would be awesome but that's 0.5GB ram.