From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: master afc0bfd380: Speed up loaddefs-generate on slow disks
Date: Thu, 02 Jun 2022 11:10:32 -0400 [thread overview]
Message-ID: <jwvee076r40.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20220602091326.514E9C009A8@vcs2.savannah.gnu.org> (Lars Ingebrigtsen's message of "Thu, 2 Jun 2022 05:13:26 -0400 (EDT)")
> Speed up loaddefs-generate on slow disks
[...]
> @@ -522,11 +522,15 @@ If INCLUDE-PACKAGE-VERSION, include package version data."
> (byte-compile-info
> (concat "Scraping files for loaddefs"))
> 0 (length files) nil 10))
> + (output-time
> + (file-attribute-modification-time (file-attributes output-file)))
> (file-count 0))
> (dolist (file files)
> (progress-reporter-update progress (setq file-count (1+ file-count)))
> (when (or (not updating)
> - (file-newer-than-file-p file output-file))
> + (time-less-p output-time
> + (file-attribute-modification-time
> + (file-attributes file))))
> (setq defs (nconc
> (loaddefs-generate--parse-file
> file output-file
I'm really surprised this is faster, even on slow disks.
Does anyone have a idea of why that is?
Maybe `file-newer-than-file-p` should accept a time value for one of the
two file names so we can speed this up further by refraining from
constructing a whole `file-attributes` only to reduce it down to
a single boolean?
Stefan
next parent reply other threads:[~2022-06-02 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165416120601.23485.9799765950267646757@vcs2.savannah.gnu.org>
[not found] ` <20220602091326.514E9C009A8@vcs2.savannah.gnu.org>
2022-06-02 15:10 ` Stefan Monnier [this message]
2022-06-02 15:20 ` master afc0bfd380: Speed up loaddefs-generate on slow disks Lars Ingebrigtsen
2022-06-02 16:16 ` Eli Zaretskii
2022-06-03 1:18 ` Stefan Monnier
2022-06-03 5:52 ` Eli Zaretskii
2022-06-03 12:21 ` Stefan Monnier
2022-06-03 13:05 ` Eli Zaretskii
2022-06-03 13:09 ` Stefan Monnier
2022-06-03 13:37 ` Eli Zaretskii
2022-06-04 12:30 ` Lars Ingebrigtsen
2022-06-05 10:06 ` Mattias Engdegård
2022-06-05 14:08 ` Lars Ingebrigtsen
2022-06-06 11:26 ` Lars Ingebrigtsen
2022-06-06 12:01 ` Alan Mackenzie
2022-06-06 12:05 ` Lars Ingebrigtsen
2022-06-06 12:08 ` Lars Ingebrigtsen
2022-06-06 12:16 ` Mattias Engdegård
2022-06-06 12:32 ` Lars Ingebrigtsen
2022-06-08 11:01 ` Lars Ingebrigtsen
2022-06-06 12:18 ` Andreas Schwab
2022-06-06 12:28 ` Lars Ingebrigtsen
2022-06-04 13:01 ` Lars Ingebrigtsen
2022-06-02 16:16 ` 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=jwvee076r40.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/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).