From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 44674@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#44674: 28.0.50; Adding current-cpu-time for performance tests
Date: Mon, 16 Nov 2020 23:09:45 +0100 [thread overview]
Message-ID: <87zh3huf6e.fsf@gnus.org> (raw)
In-Reply-To: <CAArVCkTicT1zE1pbvwe-p+mA7L_6U=spe3zR4dSTNtA9vpvbvg@mail.gmail.com> (Philipp Stephani's message of "Mon, 16 Nov 2020 19:31:47 +0100")
Philipp Stephani <p.stephani2@gmail.com> writes:
>> It does now, but we may want to change that.
>
> That would be a breaking change.
Yeah, we can't do that. But a new benchmark-run command would be fine.
>> Does it really make
>> sense to "benchmark" something using elapsed time?
>
> Yes, the benchmarks I know all measure wall time. After all, that's
> what the user cares about.
The most used benchmark every (I'm guessing), which is the "time" shell
command, reports both. Most people only care about the "real" (i.e.,
wall time), though, as you point out.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-11-16 22:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 1:07 bug#44674: 28.0.50; Adding current-cpu-time for performance tests Stefan Monnier
2020-11-16 7:13 ` Philipp Stephani
2020-11-16 7:58 ` Eli Zaretskii
2020-11-16 8:18 ` Eli Zaretskii
2020-11-16 11:46 ` Philipp Stephani
2020-11-16 17:17 ` Eli Zaretskii
2020-11-16 18:31 ` Philipp Stephani
2020-11-16 19:12 ` Eli Zaretskii
2020-11-16 22:09 ` Lars Ingebrigtsen [this message]
2020-11-16 10:11 ` Mattias Engdegård
2020-11-16 10:40 ` Eli Zaretskii
2020-11-16 10:48 ` Philipp Stephani
2020-11-16 10:53 ` Mattias Engdegård
2020-11-16 17:15 ` Eli Zaretskii
2020-11-16 15:27 ` Stefan Monnier
2020-11-16 16:14 ` Mattias Engdegård
2020-11-16 17:28 ` Eli Zaretskii
2020-11-16 17:38 ` Eli Zaretskii
2020-11-16 17:59 ` Andreas Schwab
2020-11-16 18:27 ` Eli Zaretskii
2020-11-16 18:41 ` Stefan Monnier
2020-11-16 19:22 ` Eli Zaretskii
2020-11-16 18:32 ` Philipp Stephani
2020-11-16 19:17 ` Eli Zaretskii
2020-11-16 20:10 ` Stefan Monnier
2020-11-16 18:41 ` Stefan Monnier
2020-11-16 18:39 ` Philipp Stephani
2020-11-16 19:07 ` Stefan Monnier
2020-11-16 17:13 ` Eli Zaretskii
2020-11-16 19:15 ` Mattias Engdegård
2022-04-26 13:55 ` Lars Ingebrigtsen
2022-04-26 15:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-27 13:09 ` Lars Ingebrigtsen
2022-04-27 17:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-27 17:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh3huf6e.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44674@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.