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
refactor sets use generic #112377
Merged
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
weilaaa:refactor_sets_use_generic
Oct 25, 2022
Merged
refactor sets use generic #112377
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you change these generated sets, then we won't be able to run a benchmark? I suspect the generic code may actually be slower, we should confirm how much.
The
cast
trick makes it easy to turn one of these types into a generic set if needed, without modifying the generated implementation anyway, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this will not able to run the benchmark of both. I should just expose the
cast
trick and keep generated implementation the old way.User can cast generated set to generic set on demand.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add benchmarks in the initial commit of this PR, run them (
go test -count=10 ... >/tmp/before.log
), then change the implementation and run them again, then compare (benchstat /tmp/before.log /tmp/after.log
).Why would they do that? IMHO one of the goals for this PR should be to simplify the implementation by getting rid of the code generator and instead use Go generics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if I understand you correctly. Are you referring to me doing benchmarks of different implementations in each of the two commits and then comparing the results?
But we ultimately need somewhere to record the results of the comparison. Maybe we can record the result directly in this pr conversation?
Goals the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
Yes. That's where we decide to go ahead with the refactoring or stick with the current code if we see a performance regression that is too high.