Skip to content

Conversation

@joelnn
Copy link

@joelnn joelnn commented May 25, 2018

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%.

@xerial
Copy link
Member

xerial commented May 31, 2018

@joelnn We prefer not mixing two or more changes (Unpacker and reflection). Could you make different PRs so that we can check these changes individually?

Avoiding reflection is OK, but I'm not sure about MessageUnpacker changes, so I cannot merge this PR.

@xerial xerial self-requested a review May 31, 2018 19:39
Copy link
Member

@xerial xerial left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please split PRs into two so that we can check these changes for MessageUnpacker and MessageBuffer individually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants