Added queue.getFps() function and tests for this function
Works (as expected). I consulted o3-mini-high and they approved it already.
% ./message_queue_test
Randomness seeded to: 2163801883
===============================================================================
All tests passed (63 assertions in 18 test cases)
The test didn't fail before, I think this introduces a race condition in the code.
How about getMessagesPerSecond instead getFPS?
@SzabolcsGergely while it's more accurate, I think most people are used to FPS, even if it's actually Inference per second / Messages per second. Pehraps we could go with getQueueHz(), which is also quite widely used (aka hz == fps)?
@SzabolcsGergely while it's more accurate, I think most people are used to FPS, even if it's actually Inference per second / Messages per second. Pehraps we could go with
getQueueHz(), which is also quite widely used (aka hz == fps)?
I don't see getQueueHz fit/good choice, personally. This measurement refers to queue message rate per second.