Remove sched_yield() from worker thread task pickup#435
Merged
Conversation
Seems not needed and has a big performance impact.
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.
Seems not needed and has a big performance impact, testing with hyperfine against
apriltag_demo -x 1.0 -t 4 -i 5 --family tagStandard52h13 --quiet <3 images.jpg>it leads to a 1.2x speedup against master! It makes sense if you look at the code, why should the thread yield right as it's about to execute a task?Speedup is only on linux, on macOS it has no effect