Use the inotify API on linux to improve performance #5
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
Now the gamepad extension only iterates over each input device when initialized or when there's an error while reading the inotify events. Any new input device is queried whether it's a gamepad and added if it is one every frame, so we still have plug-n-play equivalent to Windows and Emscripten.
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.
Now the gamepad extension only iterates over each input device when initialized or when there's an error while reading the inotify events. Any new input device is queried whether it's a gamepad and added if it is one every frame, so we still have plug-n-play equivalent to Windows and Emscripten.
On my system this takes the gamepad example from 20-30 FPS to 1000-1500 FPS without any optimization. With -O3, it goes from 40-50 FPS to 2000-3000 FPS.