From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: master afc0bfd380: Speed up loaddefs-generate on slow disks
Date: Sat, 04 Jun 2022 14:30:15 +0200 [thread overview]
Message-ID: <871qw48vc8.fsf@gnus.org> (raw)
In-Reply-To: <87a6avccs4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 02 Jun 2022 17:20:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
It was suggested that it might be interesting to see how our build times
have developed over time, so I had my build machine run a "make
bootstrap" each Monday going back to 2018 with this snappy one liner:
d=0; while [ $d -lt 1400 ]; do dat=`date -u -d "last Monday - $d days"`; git checkout master; git checkout `git rev-list -1 --before="$dat" HEAD`; git clean -xf; echo $dat >> /tmp/clog; { time make -j32 2>/dev/null ; } 2>>/tmp/clog; d=$(($d + 7)); done
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
Or if you prefer it in picture form:
[-- Attachment #2: Type: image/png, Size: 84237 bytes --]
[-- Attachment #3: Type: text/plain, Size: 313 bytes --]
This is with -j32, so it's quite susceptible to perturbations depending
on whether somebody did something to make the Makefile more or less
multithreaded. Which mostly explains the sudden dip at the end there,
because the build is now more parallel than ever. So it's useful to
compare with actual CPU usage:
[-- Attachment #4: Type: image/png, Size: 86878 bytes --]
[-- Attachment #5: Type: text/plain, Size: 657 bytes --]
Which is less noisy and perhaps tells us more.
Now, it's natural for Emacs build times to creep up (one might think),
as we're adding more... stuff. But there's discontinuities in the
chart, and I think we can say that something happened in the weeks
before Feb 7 2019, Sep 5 2019, May 26 2021, Feb 24 2022 and Apr 7 2022
that might be useful to look into. (Zooming on the chart on the web
page gives you the dates, if somebody wants to investigate. And also
why it seems like we're oscillating between 930 and 1150 seconds the
past few months.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-04 12:30 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 [this message]
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=871qw48vc8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.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).