Main loop profiling and disabling unnecessary parts #61
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
This is not to be merged, only suggestions on what parts are not always required to be calculated and should be skipped if applicable to gain more FPS. The code outputs time spent in each part of the computation in theoretical FPS (what FPS would that part of code achieve if it was running independently) - allows you to compare performance of operations and see the bottleneck.
|
We should probably have some benchmark branch, merged with https://github.com/allo-/virtual_webcam_background/tree/benchmark_webcam_fps (I need to rebase it on master again). I guess I can add some |
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.
This is not to be merged.
Only contains suggestions on what parts are not always required to be calculated and should be skipped if applicable to gain more FPS.
The code outputs time spent in each part of the computation in theoretical FPS (what FPS would that part of code achieve if it was running independently) - allows you to compare performance of operations and see the bottleneck.