-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Optimize sets.Set
#133231
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
base: master
Are you sure you want to change the base?
Optimize sets.Set
#133231
Conversation
Just pushed a commit with a benchmark. Here is an excerpt with the relevant output:
|
/retest |
thanks -- do we have before/after? this diff also exposes more APIs, some of which seem to be missing tests. |
I've added the same test to
|
To make it easier to see, I've combined the above results below:
|
/retest |
/retest |
/retest |
/cc @thockin |
/triage accepted |
662f298
to
84ae77f
Compare
@ash2k: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Optimize set operations and usage. Please see individual commits.
Which issue(s) this PR is related to:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig api-machinery