[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Optimizing ‘guix package’

From: Mark H Weaver
Subject: Re: Optimizing ‘guix package’
Date: Wed, 02 Apr 2014 12:58:47 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

address@hidden (Ludovic Courtès) writes:

> Mark H Weaver <address@hidden> skribis:
>> * Although I can now run union-build in 2 minutes, another full minute
>>   is spent in 'display-search-paths',
> Commit 27c6845 optimizes that (50%!).

Oooh, this makes a significant improvement on my YeeLoong :)

> The problem is that currently this is an inherently inefficient
> operation: search path information is not stored in the manifest, so
> ‘search-path-environment-variables’ has to look up the package
> corresponding to each manifest entry to find out what the search path
> variables are.  That involves traversing the module tree, which does a
> lot of I/O (this is OKish on an SSD, but much less on a real hard disk.)
> Perhaps eventually we could store search path info in manifest entries.

Sounds good to me.  When we make union smarter about handling conflicts,
it may be that some hints from the individual packages should be
consulted, and perhaps those hints should go in the manifest as well.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]