backswipeedge: don't use JIT for drag handler #4163
Merged
+0
−1
Conversation
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
While the JIT provides a speedup of around 1.6 for the drag handler, we're talking about 2.4 ms without the JIT, on a function that is called maybe 20 times a second. Plus using the JIT uses up some precious RAM.
Collaborator
|
🙏 |
1 similar comment
Collaborator
|
🙏 |
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.
As discussed in #4157
While the JIT provides a speedup of around 1.6 for the drag handler, we're talking about 2.4 ms without the JIT, on a function that is called maybe 20 times a second.
Plus using the JIT uses up some precious RAM.