Open henryptung opened 3 years ago
Thanks for opening your first issue here! Just a reminder, this forum is for Bug Reports only. Be sure to follow the issue template!
The intention was to get an initial quick reporting after starting up. Clearly it is junk. The test should probably just be image_count == 10.
This code updates the entry in the db that gets used to display the fps on the web ui console. When a camera starts up the inital fps values can vary a bit. So for the purposes of good UI we update a little quicker. The idea is that fps interval should be a useful value. Having a 1 hour report time is almost entirely useless. Any changes in value will be missed. Perhaps it should report on significant change of value.
Still that's your choice. I'll have to think on what this code should be.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
https://github.com/ZoneMinder/zoneminder/commit/046e352304a84059d02014b2d3d16cf850eaadce#diff-6bbad3965ada94cfabbe05ea66d0c4a7a8ad39a38f636ece89bef5743bc76540R1680
This commit adds a pretty weird reporting condition to the fps_report_interval check - if the frame count is less than the interval, it reports every 10 frames instead.
I have a 10FPS camera with the interval configured to every hour (interval 36000), so this ends up spamming the log 3600 times before it quiets back down to the configured cadence.
@connortechnology, not sure if this is intended? I'm not sure what the intent of the per-10-frames report is, but if more frequent updates pre-first-interval are needed for some reason, maybe it could do exponential backoff instead.
Example logs: