Administered by:
@mira@mstdn.socialI am trying out #guix installed over a fresh arch system, and I feel something is wrong. It took hours (overnight, actually) to go through bootstrap builds, which seemed to be guile builds that have not saturated CPU at all, seemed not parallelized at all, and I haven't seen much I/O wait or sys time either so not sure yet what drove wall time up. (things like building gcc go quick in comparison).
@mira I experienced something similar once, but unfortunately didn't find a root cause (couldn't repro)
#guix installs/upgrades can take some time, particularly if you get unlucky with the availability of substitutes for particular packages.
If you haven't already, I definitely recommend using `channel-with-substitutes-available` (https://guix.gnu.org/manual/en/html_node/Channels-with-Substitutes.html)
This lets you avoid compiling all those pkgdefs upfront, and also means you have better odds that the ci has your packages cached.
@shtwzrd unfortunately the substitutes I've tried did not really work on my layered system (incompatible glibc etc). I'll probably experiment a bit to see if this is a more basic problem with my setup, maybe I've missed symptoms of something like bad luks performance