From: "Mattias Engdegård" <mattiase@acm.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: master afc0bfd380: Speed up loaddefs-generate on slow disks
Date: Sun, 5 Jun 2022 12:06:30 +0200 [thread overview]
Message-ID: <04DA3B8A-8BC9-4D30-B827-8894C7DF513E@acm.org> (raw)
In-Reply-To: <871qw48vc8.fsf@gnus.org>
4 juni 2022 kl. 14.30 skrev Lars Ingebrigtsen <larsi@gnus.org>:
> I ran this three times and picked the median build time for each date,
> and viola: https://quimby.gnus.org/circus/stats-emacs/build-times.html
Thank you! I picked a few edges that looked like transitions to a higher plateau and tried to find the culprit in the logs, but it's really hard. There are many commits and nothing obvious stands out.
Things that might make it easier (speculating here):
* add commit hashes to the points in the graphs because Git dates are a bit ambiguous: are they author or commit date, what time of day are we talking about, what time zone, etc
* higher resolutions for selected periods (requires more build runs). Ideally one per commit but that would require vast amounts of time and be very noisy (many botched builds), but perhaps one per day?
I'm ashamed to admit that I looked for effects of my own attempts at speeding things up, but they were so intermingled with other changes that hard conclusions were difficult. (Mattias giveth, Alan taketh away.)
It would be very useful if we could have an automatic (or semi-automatic) daily build monitoring performance like this, perhaps even running benchmarks.
Selecting good benchmarks is hard; the elisp-benchmarks in ELPA were made by Andrea for his compilation efforts and are nigh-useless for anything else, unfortunately. I've written my own suites but again they are only useful for what measuring very specific aspects.
next prev parent reply other threads:[~2022-06-05 10:06 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 ` master afc0bfd380: Speed up loaddefs-generate on slow disks Stefan Monnier
2022-06-02 15:20 ` 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 [this message]
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=04DA3B8A-8BC9-4D30-B827-8894C7DF513E@acm.org \
--to=mattiase@acm.org \
--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).