ESP32: more accurately calculate loop rate #27967
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davidbuzz
approved these changes
Aug 31, 2024
|
testing results on esp32buzz board target: loop_rate: actual: 129.444931Hz, expected: 400Hz testing results on esp32s3empty board target: loop_rate: actual: 26.092993Hz, expected: 400Hz this highlights how terribly the s3 is scheduling right now, it was so bad the scheduler thought it was good. sigh. |
|
This matches what I see on |
Also warn about overtime on ESP32 which is most likely to hit it.
tpwrules
force-pushed
the
pr/esp-loop-rate
branch
from
3b86481 to
93b29fe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sadly it turns out the loop rate is so low in some situations that most/all samples were rejected as invalid and the loop rate converged very slowly or did not change. Increase the margin to be classified as such, and print out such excessively over loop times if the specific scheduling debug flag is enabled.