From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: More build times
Date: Thu, 30 Jun 2022 10:12:11 +0200 [thread overview]
Message-ID: <87k08yfu3o.fsf@gnus.org> (raw)
In-Reply-To: <a8238991c47b7f51686e@heytings.org> (Gregory Heytings's message of "Wed, 29 Jun 2022 16:22:08 +0000")
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
Gregory Heytings <gregory@heytings.org> writes:
> Here is the graph you wanted.
Hm; I'm unable to view that image -- Emacs says that it's invalid? I'm
not sure whether it's Gnus decoding it wrong or something, though.
But speaking of which, I've been letting an 8-code AMD server out there
do builds for a half a week now. It's not done with all the builds
(it's doing three builds per day just to get the noise level down a
bit), but here's a preliminary graph:
[-- Attachment #2: Type: image/png, Size: 70615 bytes --]
[-- Attachment #3: Type: text/plain, Size: 1787 bytes --]
> The build times are in general constant. The few commits that change
> the build time significantly, figured by breaks of the red line in the
> graph, are:
Thanks for identifying the significant commits.
> d12e5d003d deterioration from 78s to 95s (22%) Daniel Colascione Add
> portable dumper
That's that big jump in January 2019 in the chart above. I wonder
whether anybody's taken a look at it again to see if there's anything
that can be done more efficiently there.
> a350ae058c deterioration from 108s to 129s (19%) Stefan Monnier
> <monnier@iro.umontreal.ca> * lisp/emacs-lisp/cconv.el: Improve line-nb
> info of unused var warnings
Hm... is that something that can be improved (if that code is still
there, that is)?
> fddd63f8b8 and b3d310fa96 deterioration from 129s to 140s (9%) Glenn
> Morris <rgm@gnu.org> Distribute the real source for some doc/misc
> manuals (bug#45143)
Ah, I suspected that that was the cause of one of the major jumps.
> fd31ef21c5 deterioration from 126s to 132s (5%) Alan Mackenzie Don't
> use 'load-read-function' in byte-compile-from-buffer
> f687e62ac5 deterioration from 132s to 145s (10%) Alan Mackenzie Fix
> symbols with position appearing in the output of 'compile-defun'
> 6092ee1c3f improvement from 145s to 130s (10%) Alan Mackenzie Amend
> byte-run-strip-symbol-positions so that an unexec build builds
> 68cdb95019 deterioration from 130s to 136s (5%) Alan Mackenzie Restore
> call to byte-run-strip-symbol-positions in byte-compile-out
Right; so these weren't in one big commit, so it's more spread out.
> Congrats for 1d4e903417, 3e312d11ce and 73a384a986!
Thanks. 😃
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-30 8:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 12:17 More build times Lars Ingebrigtsen
2022-06-25 13:44 ` Lars Ingebrigtsen
2022-06-25 13:51 ` Tor Kringeland
2022-06-25 14:41 ` Lars Ingebrigtsen
2022-06-25 15:15 ` Andreas Schwab
2022-06-25 14:16 ` Eli Zaretskii
2022-06-25 14:44 ` Lars Ingebrigtsen
2022-06-25 15:16 ` Eli Zaretskii
2022-06-25 15:30 ` Lars Ingebrigtsen
2022-06-29 16:22 ` Gregory Heytings
2022-06-30 8:12 ` Lars Ingebrigtsen [this message]
2022-06-30 8:30 ` Gregory Heytings
2022-06-30 8:47 ` Stephen Berman
2022-06-30 8:49 ` Lars Ingebrigtsen
2022-06-30 8:42 ` Andreas Schwab
2022-06-30 8:55 ` Stephen Berman
2022-06-30 16:07 ` Juri Linkov
2022-06-30 16:31 ` Andreas Schwab
2022-06-30 17:10 ` Juri Linkov
2022-06-30 13:27 ` Mattias Engdegård
2022-06-30 17:50 ` Gregory Heytings
2022-06-30 17:53 ` Gregory Heytings
2022-06-25 14:34 ` Yuri Khan
2022-06-25 14:49 ` Lars Ingebrigtsen
2022-06-26 8:30 ` Stefan Monnier
2022-06-26 15:38 ` Lars Ingebrigtsen
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=87k08yfu3o.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.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).