Re: How many bytes do we add (closure of guix) when adding one new package?

Simon Tournier skribis: > Hi Jack, > > On Tue, 30 May 2023 at 16:55, Jack Hill wrote: > >> $ ~/.config/guix/current/lib/guile/3.0/site-ccache/gnu [env]$ sudo compsize . >> Processed 595 files, 1659 regular extents (1659 refs), 0 inline. >> Type Perc Disk Usage Uncompressed

Re: Faster “guix search” (was Re: How many bytes do we add (closure of guix) when adding one new package?)

> It makes zero sense to load full package definitions from disk for > most queries, such as guix search, with an SoA representation we > could load only the fields that we care about. i'd like to quickly point out something while we are discussing this: when i came to guix it was rather

Re: Faster “guix search” (was Re: How many bytes do we add (closure of guix) when adding one new package?)

Simon Tournier writes: > Hi, > > On Tue, 30 May 2023 at 21:10, Csepp wrote: > >> It makes zero sense to load full package definitions from >> disk for most queries, such as guix search, with an SoA representation >> we could load only the fields that we care about. > > That’s

Faster “guix search” (was Re: How many bytes do we add (closure of guix) when adding one new package?)

Hi, On Tue, 30 May 2023 at 21:10, Csepp wrote: > It makes zero sense to load full package definitions from > disk for most queries, such as guix search, with an SoA representation > we could load only the fields that we care about. That’s already the case; see

Re: How many bytes do we add (closure of guix) when adding one new package?

Hi Jack, On Tue, 30 May 2023 at 16:55, Jack Hill wrote: > $ ~/.config/guix/current/lib/guile/3.0/site-ccache/gnu [env]$ sudo compsize . > Processed 595 files, 1659 regular extents (1659 refs), 0 inline. > Type Perc Disk Usage Uncompressed Referenced > TOTAL 21% 36M

Re: How many bytes do we add (closure of guix) when adding one new package?

On Tue, 30 May 2023, Simon Tournier wrote: Just to put a figure on what means “big”: currently the .go files are 5 times bigger than their associated .scm. Somehow, it’s the trap of DSL. :-) Packages are declarative and the information they declare is not dense. However, because they are

Re: How many bytes do we add (closure of guix) when adding one new package?

Simon Tournier writes: > Hi, > > On ven., 26 mai 2023 at 18:21, Ludovic Courtès wrote: > >> I agree that .go files are quite big (.scm files as well, but we’ve >> improved information density somewhat by removing input labels :-)). >> >> The size of .go files went down when we switch to the

Re: How many bytes do we add (closure of guix) when adding one new package?

Hi, On ven., 26 mai 2023 at 18:21, Ludovic Courtès wrote: > I agree that .go files are quite big (.scm files as well, but we’ve > improved information density somewhat by removing input labels :-)). > > The size of .go files went down when we switch to the baseline compiler > (aka. -O1): > >

Re: How many bytes do we add (closure of guix) when adding one new package?

Hello! Thanks for the detailed analysis! Simon Tournier skribis: > Conclusions: > > 1. the addition of one package leads to an increase of ~ 12 KiB > > 2. the core of Guix is about ~ 62 MiB > > 3. doubling the number of packages is doubling the size to download at > “guix pull” time. I

How many bytes do we add (closure of guix) when adding one new package?

Hi, The initial discussion was about the closure of Guix and that “guix pull” brings graphical libraries. See #63050 [1]. Here, I would like to open a discussion about how Guix scales, i.e. about its size. I am trying to answer the question I am asking as the subject. ;-) It’s another angle