[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44674: 28.0.50; Adding current-cpu-time for performance tests
From: |
Lars Ingebrigtsen |
Subject: |
bug#44674: 28.0.50; Adding current-cpu-time for performance tests |
Date: |
Mon, 16 Nov 2020 23:09:45 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
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
bug#44674: 28.0.50; Adding current-cpu-time for performance tests, Mattias Engdegård, 2020/11/16
bug#44674: 28.0.50; Adding current-cpu-time for performance tests, Stefan Monnier, 2020/11/16