unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Emacs-devel@gnu.org
Subject: More build times
Date: Sat, 25 Jun 2022 14:17:15 +0200	[thread overview]
Message-ID: <87czexj5tg.fsf@gnus.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 119 bytes --]

The last week, my build machine has been running a whole bunch of
builds, and here's a chart for the last few months:


[-- Attachment #2: Type: image/png, Size: 70049 bytes --]

[-- Attachment #3: Type: text/plain, Size: 43 bytes --]


What's odd are those peaks.  Let's zoom:


[-- Attachment #4: Type: image/png, Size: 64132 bytes --]

[-- Attachment #5: Type: text/plain, Size: 89 bytes --]


Some builds consistently take 40s longer to run.  And here's what's even
more bizarre:


[-- Attachment #6: Type: image/png, Size: 68965 bytes --]

[-- Attachment #7: Type: text/plain, Size: 1190 bytes --]


Those exact same builds take a lot less CPU to run.  So...  less CPU
usage; more real time?  It's bizarre, and perhaps it's just a measuring
artefact of some kind?

Anybody see the same phenomenon on their systems?  (These are clean
builds -- made from a fresh git clone.)

Here's the data in CSV form:

20220602,f71cfd3084,92.74,1101.11
20220603,8f279c8666,92.73,1099.27
20220604,6f69284ada,94.41,1096.24
20220605,1b8719835a,132.86,951.54
20220606,0a36671f41,92.30,1109.85
20220607,8c252e2326,93.21,1114.62
20220608,88b025f815,93.08,1116.36
20220609,d02c94090c,131.41,952.02
20220610,8ef3862fa0,92.34,1111.84
20220611,3247c31d67,91.62,1101.95
20220612,98365c7b1e,93.69,1090.07
20220613,72e0ef74d0,93.58,1114.55
20220614,5678829a62,92.87,1112.83
20220615,787c4ad8b0,94.85,1105.01
20220616,556c304007,93.11,1109.08
20220617,f419de6eca,132.49,957.99
20220618,0d103e6f79,89.38,1084.58
20220619,8b45e7c681,88.23,1074.94
20220620,3947037a33,89.66,1085.17
20220621,4ae315f7c3,89.31,1084.66
20220622,b1af8c2c00,68.61,700.41
20220623,b1af8c2c00,68.15,699.24
20220624,b1af8c2c00,68.16,700.60


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no


             reply	other threads:[~2022-06-25 12:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 12:17 Lars Ingebrigtsen [this message]
2022-06-25 13:44 ` More build times 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
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=87czexj5tg.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).