4 ms·

std::chrono counts the number of ticks of a given periodicity. The periodicity does have to be a known compile-time ratio expressible as a fraction of seconds,

by mpyne 9mo ago

std::chrono counts the number of ticks of a given periodicity. The periodicity does have to be a known compile-time ratio expressible as a fraction of seconds, but you can use a floating-type type to count the number of ticks. std::chrono is meant to take advantage of information about periodicity at compile time, but if you want to count in terms of a dynamic periodicity not known until runtime, you can still do things. E.g. use time_t and some wrapper functions, or just pick one (or several) std::chrono base durations such as standardizing on nanoseconds, and then just count floating-point ticks.

loeg 9mo ago
> The periodicity does have to be a known compile-time ratio expressible as a fraction of seconds Right, that's the problem I'm describing. > or just pick one (or several) std::chrono base durations such as standardizing on nanoseconds, and then just count floating-point ticks. None of this really fits well -- the idea is to count in integer ticks (invariant cycles), without doing expensive division or floating point math. It's like steady clock, but in ticks instead of nanos.
- maxnoe 9mo ago
  But on any modern CPU, clock speed won't be constant. It's not compile time constant, nor a runtime constant. Its variable over time. You'd have to record the clock speed over time and the ticks, so why not just record actual time?
  - loeg 9mo ago
    You missed this key part of my earlier comment: > (invariant cycles) All major CPUs have had invariant cycle counters for decades at this point. It is a runtime constant.
  - adrian_b 9mo ago
    The CPU clock varies, but all modern CPUs have some counter that is incremented at a constant frequency, like the Time Stamp Counter (TSC) on Intel/AMD CPUs. When discussing hardware clock ticks used for time measurement, the ticks from TSC or similar counters are meant and not ticks from some counter that counts cycles of the CPU clock, like provided by the performance counters. The variable CPU clock frequency can be measured by computing the ratio between the ticks accumulated by the corresponding performance counter and the ticks accumulated by the TSC (or similar counter), for which the clock frequency is constant and known.

by mpyne 9mo ago

loeg 9mo ago

> The periodicity does have to be a known compile-time ratio expressible as a fraction of seconds Right, that's the problem I'm describing. > or just pick one (or several) std::chrono base durations such as standardizing on nanoseconds, and then just count floating-point ticks. None of this really fits well -- the idea is to count in integer ticks (invariant cycles), without doing expensive division or floating point math. It's like steady clock, but in ticks instead of nanos.

maxnoe 9mo ago
But on any modern CPU, clock speed won't be constant. It's not compile time constant, nor a runtime constant. Its variable over time. You'd have to record the clock speed over time and the ticks, so why not just record actual time?
- loeg 9mo ago
  You missed this key part of my earlier comment: > (invariant cycles) All major CPUs have had invariant cycle counters for decades at this point. It is a runtime constant.
- adrian_b 9mo ago
  The CPU clock varies, but all modern CPUs have some counter that is incremented at a constant frequency, like the Time Stamp Counter (TSC) on Intel/AMD CPUs. When discussing hardware clock ticks used for time measurement, the ticks from TSC or similar counters are meant and not ticks from some counter that counts cycles of the CPU clock, like provided by the performance counters. The variable CPU clock frequency can be measured by computing the ratio between the ticks accumulated by the corresponding performance counter and the ticks accumulated by the TSC (or similar counter), for which the clock frequency is constant and known.