use MessageBuffer constructor reflection only when required#478
Merged
xerial merged 1 commit intomsgpack:developfrom Oct 18, 2018
Merged
use MessageBuffer constructor reflection only when required#478xerial merged 1 commit intomsgpack:developfrom
xerial merged 1 commit intomsgpack:developfrom
Conversation
Author
|
Thoughts on merging this? |
Member
|
OK. This optimization looks nice if we are using only MessageBuffer. |
Member
|
Merged. |
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.
Invoking the MessageBuffer constructor showed up as a hotspot in my profiling. There is no need for it when we are only using MessageBuffer itself, not one of the subclasses.
This patch improves unpackValue performance for my data by about 25%.
(previously #477)