[PERFORMANCE] Use static TypeToken for complex CQL types#456
Merged
chibenwa merged 2 commits intoapache:masterfrom May 24, 2021
Merged
[PERFORMANCE] Use static TypeToken for complex CQL types#456chibenwa merged 2 commits intoapache:masterfrom
chibenwa merged 2 commits intoapache:masterfrom
Conversation
There computing take up to 1,3% of CPU time, doing reflection over and over again to build them.
For Row types they are already known, and their lookup takes and additional 0.5% of CPU.
Arsnael
approved these changes
May 24, 2021
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.
There computing take up to 1,3% of CPU time, doing reflection
over and over again to build them.
See the following flame graphs: