From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: p.stephani2@gmail.com, 44674@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#44674: 28.0.50; Adding current-cpu-time for performance tests
Date: Mon, 16 Nov 2020 20:15:26 +0100 [thread overview]
Message-ID: <B9048BB0-5887-4ABA-AE7D-DB915CE10EAF@acm.org> (raw)
In-Reply-To: <834klptece.fsf@gnu.org>
16 nov. 2020 kl. 18.13 skrev Eli Zaretskii <eliz@gnu.org>:
>> Perhaps not ideal to cons in a timing primitive where low overhead is called for.
>> What about just returning an integer and have a different way to get at TICKS-PER-SEC?
>
> Why not just return a float in seconds instead?
Precision would vary depending on the magnitude of the time stamp (which should be irrelevant since only differences are used). Floats are also always boxed, for that matter.
> Can you make a case for process-global timing, given that we don't
> control all of the threads, and that some of them are utterly
> unrelated to timing Lisp programs?
If Lisp actions trigger work done in other threads the completion of which has to be awaited then those threads are effectively part of the same computation. (Admitted, not a very strong case.)
next prev parent reply other threads:[~2020-11-16 19:15 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
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 [this message]
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
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=B9048BB0-5887-4ABA-AE7D-DB915CE10EAF@acm.org \
--to=mattiase@acm.org \
--cc=44674@debbugs.gnu.org \
--cc=eliz@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 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).