-
Notifications
You must be signed in to change notification settings - Fork 204
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
chore: Create state.Node
interface methods to access cluster state details
#152
chore: Create state.Node
interface methods to access cluster state details
#152
Conversation
1170f22
to
5251ce7
Compare
8c567a2
to
ef4bca4
Compare
911a232
to
cfff5af
Compare
Before PR === RUN TestSchedulingProfile
scheduled 7610 against 21 nodes in total in 3.927209844s 1937.7625088271193 pods/sec
400 instances 10 pods 1 nodes 3.157028ms per scheduling 315.702µs per pod
400 instances 100 pods 1 nodes 32.386241ms per scheduling 323.862µs per pod
400 instances 500 pods 1 nodes 148.849796ms per scheduling 297.699µs per pod
400 instances 1000 pods 3 nodes 338.482729ms per scheduling 338.482µs per pod
400 instances 1500 pods 4 nodes 536.756792ms per scheduling 357.837µs per pod
400 instances 2000 pods 5 nodes 648.753041ms per scheduling 324.376µs per pod
400 instances 2500 pods 6 nodes 736.882146ms per scheduling 294.752µs per pod
--- PASS: TestSchedulingProfile (13.59s)
PASS After PR === RUN TestSchedulingProfile
scheduled 7610 against 20 nodes in total in 4.016303065s 1894.7773305050625 pods/sec
400 instances 10 pods 1 nodes 3.097744ms per scheduling 309.774µs per pod
400 instances 100 pods 1 nodes 32.313276ms per scheduling 323.132µs per pod
400 instances 500 pods 1 nodes 153.221583ms per scheduling 306.443µs per pod
400 instances 1000 pods 3 nodes 339.300361ms per scheduling 339.3µs per pod
400 instances 1500 pods 4 nodes 541.017812ms per scheduling 360.678µs per pod
400 instances 2000 pods 4 nodes 588.58475ms per scheduling 294.292µs per pod
400 instances 2500 pods 6 nodes 792.721666ms per scheduling 317.088µs per pod
--- PASS: TestSchedulingProfile (14.09s)
PASS Effectively the same benchmarking between before/after PR |
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.
nice changes -- let's hope those tests hold ;)
72716d8
to
c0b9477
Compare
c0b9477
to
d67c432
Compare
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.
lgtm, performance impact is small and worth the flexibility IMO
Fixes #
Description
state.Node
interface methods to access cluster state detailsProvisioner
fromExistingNode
so thatExistingNodes
can be built purely based onstate.Node
How was this change tested?
make presubmit
FOCUS=Scheduling make e2etests
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.