From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 40628@debbugs.gnu.org, phillip lord <phillip.lord@russet.org.uk>
Subject: bug#40628: Optimize admin/nt dependency computation
Date: Sat, 08 Aug 2020 14:57:00 +0200 [thread overview]
Message-ID: <87k0y91ejn.fsf@gnus.org> (raw)
In-Reply-To: <854ktmyq7s.fsf@gmail.com> (Noam Postavsky's message of "Tue, 14 Apr 2020 12:41:43 -0400")
Noam Postavsky <npostavs@gmail.com> writes:
> While checking the patch I suggested in
> https://debbugs.gnu.org/40003#11, I noticed the dependency extraction
> seemed pretty slow. With the patch attached below it's much faster
> (1m20.437s to 0m3.695s according to 'time ./build-dep-zips.py -l').
>
>>From 5312f51e315cc147ca901d499aa3c3cc64aa3340 Mon Sep 17 00:00:00 2001
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Tue, 14 Apr 2020 12:27:34 -0400
> Subject: [PATCH] Optimize admin/nt dependency computation
>
> admin/nt/dist-build/build-dep-zips.py (immediate_deps)
> (extract_deps): Gather package dependency info in batches, rather than
> one at a time. This reduces the number of invocations of 'pacman -Si
> ...' to the depth of the dependency tree, rather than the number of
> dependent packages.
> (top-level): Don't call 'extract_deps' when given the '-l' option.
This was four months ago, but the patch was apparently not applied?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-08 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 16:41 bug#40628: Optimize admin/nt dependency computation Noam Postavsky
2020-08-08 12:57 ` Lars Ingebrigtsen [this message]
2020-08-18 13:58 ` Lars Ingebrigtsen
2021-11-12 9:23 ` Lars Ingebrigtsen
2021-11-12 9:55 ` Andy Moreton
2021-11-14 1:06 ` Lars Ingebrigtsen
2021-11-12 12:03 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0y91ejn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=40628@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=phillip.lord@russet.org.uk \
/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/emacs.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).