Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WBWI Internal Move implementation from .h into .cpp #8229

Closed
wants to merge 1 commit into from

Conversation

adamretter
Copy link
Collaborator

Moves some of the structural refactoring from #8135 into this PR.
This just cleans up the code by moving implementation out of the .h file and into the .cc file.

Should be considered for merge before both #7214 and #8135

Copy link
Contributor

@mrambacher mrambacher left a comment

Choose a reason for hiding this comment

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

LGTM.

@facebook-github-bot
Copy link
Contributor

@mrambacher has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@mrambacher merged this pull request in 2760c2a.

Copy link
Contributor

@ajkr ajkr left a comment

Choose a reason for hiding this comment

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

I think it deserves a benchmark comparison. Also we may benefit from declaring BaseDeltaIterator a final class.

@adamretter
Copy link
Collaborator Author

@ajkr I was surprised to see your suggestion for a benchmark here. I did not expect that moving the implementation from the .h file to the .cc file would have an impact. Have seen such issues in the past?

@ajkr
Copy link
Contributor

ajkr commented Apr 27, 2021

I don't remember. More generally, we have seen a big difference in performance with vs. without inlining function calls. My guess is that this change doesn't affect inline-ability except in rare cases (e.g., build with profile-guided optimization and without link-time optimization - BaseDeltaIterator clients may speculatively devirtualize callsites to regular function calls, which can only be inlined when definitions are in the header).

I think it's hard to prove so wouldn't suggest trying much beyond benchmarks with default build settings. I can't think of why it would change in that case.

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

Successfully merging this pull request may close these issues.

4 participants