unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-devel@gnu.org
Subject: Re: More build times
Date: Sat, 25 Jun 2022 16:44:55 +0200	[thread overview]
Message-ID: <878rpkiyzc.fsf@gnus.org> (raw)
In-Reply-To: <83y1xkakvs.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Jun 2022 17:16:39 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> You mean the build times include the time it took Git to checkout the
> tree at a specific commit?

No, it just measures the "make".

>> No intervening commits or anything, but checking out f419de6eca and
>> 61a312ba0c give you vastly different trees -- presumably because of
>> merges and the like (since f419de6eca4 originated in emacs-28).
>
> could explain that the elapsed time increased whereas CPU time
> decreased: if you get more files that look modified to Make, you
> should see more CPU time invested into rebuilding.  Am I missing
> something?

Yes.  "git checkout f419de6eca4ca6" (on the master branch) does not give
you the state on master branch at that time.  Try it yourself:

git checkout f419de6eca4ca6
...
HEAD is now at f419de6eca * lisp/textmodes/artist.el: Minor doc fixes.
larsi@xo:~/src/emacs/bench$ ls -l lisp/emacs-lisp/load*
ls: cannot access 'lisp/emacs-lisp/load*': No such file or directory

And that file does exist on master at that time.

git is so much fun.

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



  reply	other threads:[~2022-06-25 14:44 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 [this message]
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=878rpkiyzc.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=Emacs-devel@gnu.org \
    --cc=eliz@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).