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: Tue, 29 Aug 2023 11:19:56 +0200 [thread overview]
Message-ID: <874jkiw6gz.fsf@gnu.org> (raw)
In-Reply-To: <dzkxWsiO2j2SlWZLTruNGXIELUDvT0_JRUOCJEnE2zlG13OyB1x6ohriYL8-mUHgg2mjtLoOXKASNm-bRVLw6tgkUrVgDH46PaNxdT4oXm8=@protonmail.com> (Luis Felipe's message of "Sun, 27 Aug 2023 17:59:28 +0000")
Hi Luis,
Luis Felipe <luis.felipe.la@protonmail.com> skribis:
> I still use the same computer with the same hard drive, and performance has improved when installing packages. Running
>
> $ time guix package -i perl --max-jobs=1
>
> initially took
>
> (87 packages in profile)
> real 8m3,043s
> user 0m2,656s
> sys 0m0,239s
>
> But now (guix 17fadbb), it takes
>
> (96 packages in profile)
> real 3m51,058s
> user 0m7,490s
> sys 0m0,788s
I think it’s not good.
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 thread contains an analysis of specific sources of slowness, such as
the cost of building the XDG MIME database:
https://issues.guix.gnu.org/44053
I think we’re not done; we can probably do better by first figuring out
which parts take time (profiling) and then addressing specific issues.
Ludo’.
next prev parent reply other threads:[~2023-08-29 9:21 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 [this message]
2023-08-29 21:51 ` Luis Felipe via Bug reports for GNU Guix
2023-09-09 11:02 ` 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=874jkiw6gz.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).