From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix size reduction work group
Date: Mon, 10 Feb 2020 00:45:58 +0100 [thread overview]
Message-ID: <CAJ3okZ3T17OU3ER9nfVDWAQQz2EY+hx4XuRs33j=Lr1Nz-t-LA@mail.gmail.com> (raw)
In-Reply-To: <875zghdo7j.fsf@ambrevar.xyz>
Hi Pierre,
On Sat, 8 Feb 2020 at 17:43, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> >> - Improve the tooling. In my experience, guix graph is quickly unusable
> >> with a high number of nodes. Maybe d3.js could be leveraged to add a
> >> filtering system, or a way to click on nodes to hide them and all
> >> their children.
> >
> > ‘guix size’ is key here: it’s a profiler, exactly what we need IMO.
> > WDYT?
>
> Maybe I'm missing something, but in general I think that guix size only
> gives a birds eye view and does not allow for closer inspection.
>
> Say FOO has BAR in its closure, but not in the explicit inputs, how can
> I figure out which of the indirect inputs drags BAR in?
I do not understand what you are looking for, but there is already:
guix graph -t reverse-package
guix graph -t reverse-bag
that does more or less what I understand you want.
> With an extensive guix graph, it quickly becomes impossible to follow
> the millions of arrows.
Using a static graphviz, I agree. And I generally end up by grepping
directly in the 'dot' output file.
Maybe something more dynamic using 'd3.js' or similar to view *big*
graphs could help.
> What I'd like to have is an interactive graph that I can trim to links
> between given nodes. This would allow me to ask "give me the dependency
> chain that links FOO and BAR".
I agree that tools to work with the graph would be welcome.
Currently, the graph is here but under-used, IMHO.
The first step seems to list what operations and filtering is missing.
> > The thing is, I think it’s something that requires constant care, every
> > time we add a package or modify an existing one. It’s very easy to lose
> > benefits that had been previously obtained through hard work!
>
> This is a good point. "Adding" a package is less critical since it does
> not impact the closure size of the rest. For "updates" maybe we could
> leverage the continuous integration to flag a warning when a new build
> has increased the size of the package compared to a previous build by
> some threshold.
You could propose such feature to the Guix Data Service.
For example, on this webpage [1], the history of all the Git package
in Guix is shown. The closure size could be reported.
[1] http://data.guix.gnu.org/repository/1/branch/master/package/git
All the best,
simon
next prev parent reply other threads:[~2020-02-09 23:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:57 Guix size reduction work group Pierre Neidhardt
2020-02-04 16:22 ` zimoun
2020-02-04 17:59 ` Julien Lepiller
2020-02-05 15:18 ` Ludovic Courtès
2020-02-05 16:11 ` zimoun
2020-02-07 21:35 ` Ludovic Courtès
2020-02-07 22:31 ` Gábor Boskovits
2020-02-08 13:40 ` zimoun
2020-02-10 13:13 ` Tobias Geerinckx-Rice
2020-02-11 14:15 ` Ludovic Courtès
2020-02-08 16:43 ` Pierre Neidhardt
2020-02-09 23:45 ` zimoun [this message]
2020-02-10 8:09 ` Pierre Neidhardt
2020-02-10 8:46 ` Christopher Baines
2020-02-11 14:17 ` Ludovic Courtès
2020-02-10 10:30 ` zimoun
2020-02-10 12:33 ` Julien Lepiller
2020-02-11 14:20 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ3T17OU3ER9nfVDWAQQz2EY+hx4XuRs33j=Lr1Nz-t-LA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).