From: "Ludovic Courtès" <ludo@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: 44053@debbugs.gnu.org, jbranso@dismail.de
Subject: bug#44053: Poor profile generation performance on spinning disks
Date: Sat, 09 Sep 2023 13:02:11 +0200 [thread overview]
Message-ID: <87zg1vy5ho.fsf@gnu.org> (raw)
In-Reply-To: <mSj2EYYJvpknifEjHBEvx96jRolchzWAitRR1aPwzJ_5vubGRYl9TIPoBxZrcf0tmN-bcXiXfkpXTL-vNy-S2ekb9K4_D6somthxsXamoYQ=@protonmail.com> (Luis Felipe's message of "Tue, 29 Aug 2023 21:51:29 +0000")
Hi Luis,
Luis Felipe <luis.felipe.la@protonmail.com> skribis:
>> Could you time just profile generation itself?
>>
>
>> To do that, you need to find the profile generation and then to rebuild
>> it, along these lines:
>>
>
>> DRV=$(guix gc --derivers $(readlink -f ~/.guix-profile))
>> time guix build --check $DRV
>
> The above results in
>
> real 1m28,841s
> user 0m2,169s
> sys 0m0,450s
Thanks.
It means that profile generation itself (and not just hooks) is slow.
The place to look at is (guix build union). Unfortunately, I suspect
there’s little room for optimization at this stage (see commit
12129998689648923b58c426362a1bc875da75f9 from… 2014).
Fundamentally, ‘union-build’ traverses every input directory, which is
expensive with low-end hard disks. It would still be worth
investigating (for example by strace’ing the ‘union-build’ process) in
case we missed optimizationm opportunities, though.
Thanks,
Ludo’.
prev parent reply other threads:[~2023-09-09 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 3:35 bug#44053: Poor profile generation performance on spinning disks Maxim Cournoyer
2020-10-18 23:05 ` Luis Felipe via Bug reports for GNU Guix
2020-10-19 8:18 ` zimoun
2020-10-19 18:18 ` Maxim Cournoyer
2022-03-23 12:38 ` zimoun
2022-03-23 16:17 ` Maxim Cournoyer
2022-03-23 16:54 ` zimoun
2023-08-26 22:11 ` jbranso--- via Bug reports for GNU Guix
2023-08-27 17:59 ` Luis Felipe via Bug reports for GNU Guix
2023-08-29 9:19 ` Ludovic Courtès
2023-08-29 21:51 ` Luis Felipe via Bug reports for GNU Guix
2023-09-09 11:02 ` Ludovic Courtès [this message]
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=87zg1vy5ho.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44053@debbugs.gnu.org \
--cc=jbranso@dismail.de \
--cc=luis.felipe.la@protonmail.com \
/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).