Skip to content

Performance: Automatically adjust next poll period to account for network latency #30

@RolandPheasant

Description

@RolandPheasant

High cpu usgae has been reported see issue #14

I think this is caused by the work to check for and load changes from the file is longer than the poll interval. So to remedy I will try the following

  1. Slow down poll rate
  2. Only start timer for next poll after the work in the previous poll is complete

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions