NINJA_STATUS %o, %c

Question

NINJA_STATUS %o, %c

bartoszek opened this issue 4 years ago · comments

Are there any limitations preventing the implementation of %c, %o rate info in NINJA_STATUS, or ware they drop intentionally.

Michael Forney · Answer 1 · Mon Jun 22 2020 02:15:18 GMT+0800 (China Standard Time)

I don't think there is any limitation preventing their implementation. Maybe @E5ten can comment about why those were excluded.

Any patches are welcome.

E5ten · Answer 2 · Mon Jun 22 2020 02:35:36 GMT+0800 (China Standard Time)

I just didn't know how to, so I left them out.

Deleted user · Answer 3 · Sat Jul 25 2020 09:14:55 GMT+0800 (China Standard Time)

How would %c be implemented in particular?
Keeping track of the number of edges finished over the last second? That is a whole number rather than a float, but Ninja seems to use a float for %c.

We might also keep track of the time between the last two finished edges. Then 1/(time between last two, i.e. 0.2 sec) = rate (e.g. 5 edges/sec), or average over the times between the last 3, 4 finished etc. Can't fully understand what the ninja manual says.