Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polling rate of 60s (or frequency of 1/60s) results in extreme unresponsiveness #4

Open
MatthAlex opened this issue Jan 16, 2025 · 0 comments

Comments

@MatthAlex
Copy link
Collaborator

Issue

Started an experiment with a polling rate of 60s, which ran for 2+ days.

The UI controls, tabs, export functionality, all felt very sluggish throughout.

key observations

  • This experiment and stress test used the exact same setup; RPI4 + ADC
  • polling rate of 60s is 30 times less data points than the 4.5 day stress test
  • stress test's UI and functionality was usable through the first 2 days
  • approximate number of points is <5k
  • initial test with downsampling (iloc 1 every 10 points) worked very well, with around 17k points
  • 60s poll rate was not tested for usability; may be a particular bad configuration

Possible Explanation

The call to the device is blocking; the linear execution of the app may result in slowdowns on every piece of functionality.

Possible Solution

Investigate async/await for the device calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant