Attempt to improve CPU use by declaring things const#2210
Merged
glowtape merged 3 commits intod-ronin:nextfrom May 22, 2018
Merged
Attempt to improve CPU use by declaring things const#2210glowtape merged 3 commits intod-ronin:nextfrom
glowtape merged 3 commits intod-ronin:nextfrom
Conversation
Also avoid a copy of msg in event pumping.
Member
|
L1690 in uavobjectmanager.c needs const. Gives slight improvements, still not as far as reverting those commits mentioned in #2200. |
Note this requires that the frequency be 1000. Optimizer couldn't suppress the math because of edge case when time near 0.
Member
Author
|
OK, one more thing to try in here. |
Member
Author
|
I'd advocate for this to merge-- with the PIOS_Thread time change we're back to where we were originally in CPU use. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Also just assume systime is milliseconds because the math before was faulty.
May improve #2200