You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Python 3.7 there is time.monotonic_ns(), which allows us to use nanoseconds for measuring walltime.
This makes sense only if we switch from using float to Decimal for storing these values, as the main reason why time.monotonic() is less precise is the use of float. This will change the types used in the public API of RunExecutor, but we have documented already that these values can be some arithmetic type and we have not guaranteed them to be floats. So we should be able to do this.
Then we should also return CPU-time measurements as Decimal values. (For these we already read micro- or nanosecond values from the kernel, but loose precision by converting them to float.)
The text was updated successfully, but these errors were encountered:
Since Python 3.7 there is
time.monotonic_ns()
, which allows us to use nanoseconds for measuring walltime.This makes sense only if we switch from using
float
toDecimal
for storing these values, as the main reason whytime.monotonic()
is less precise is the use offloat
. This will change the types used in the public API ofRunExecutor
, but we have documented already that these values can be some arithmetic type and we have not guaranteed them to befloat
s. So we should be able to do this.Then we should also return CPU-time measurements as
Decimal
values. (For these we already read micro- or nanosecond values from the kernel, but loose precision by converting them tofloat
.)The text was updated successfully, but these errors were encountered: