bug#55499: closed (excessively large manifests due to propagation)

[GNU bug Tracking System]

Your message dated Fri, 01 Jul 2022 23:54:41 +0200
with message-id <878rpc33dq.fsf@gnu.org>
and subject line Re: bug#55499: excessively large manifests due to propagation
has caused the debbugs.gnu.org bug report #55499,
regarding excessively large manifests due to propagation
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
55499: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55499
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> excessively large manifests due to propagation
>
>
>
>
> Date: 
>
> Wed, 18 May 2022 15:53:06 +0200
>
>
>
>
> User-agent: 
>
> mu4e 1.6.10; emacs 28.0.50
>
>
>
>
> Packages of some languages rely heavily on propagation.  R is one
> example.  Since the generated “manifest” file of a Guix profile records
> entries for all propagated packages, this can get really big really
> quickly.
>
> A profile consisting only of four R packages (r-seurat, r-cistopic,
> r-monocle3, and r-cicero-monocle3) results in a “manifest” file that
> weighs 7.1MB.  At the MDC I repeatedly encountered manifest files that
> are exceeding 24MB.
>
> Simply reading that big a file with
>
>     (call-with-input-file "huge-manifest" read)
>
> takes several seconds.  On the MDC cluster I observed a delay of about
> 27 seconds.
>
> Disabling read positions with (read-disable 'positions) significantly
> speeds this up (18s vs 27s), but it’s still very slow.
>
> We may be able to speed things up by supporting definitions or
> references in manifest files, so that we don’t need to repeat a sub-tree
> when generating the file.
>
> -- 
> Ricardo
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#55499: excessively large manifests due to propagation
>
>
>
>
> Date: 
>
> Fri, 01 Jul 2022 23:54:41 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
>
>
>
>
> Hi!
>
> I went ahead and pushed it as 4ff12d1de7cd617b791996ee7ca1240660b4c20e.
>
> Ludo’.
>
>
> --- End Message ---