-
Notifications
You must be signed in to change notification settings - Fork 264
Conversation
|
||
## OBJECTIVE | ||
|
||
- Comparing the scheduler performance of kube-batch with the scheduler performance of the default scheduler |
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.
Our objective is to evaulate performance of kube-batch; it's not necessary to compare with default scheduler.
|
||
## DESIGN OVERVIEW | ||
|
||
We assume that we want to benchmark a test T across two variants A(with default scheduler) and B(with kube-batch scheduler). |
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.
Nop, only evaulate kube-batch's performance is ok.
@k82cn updated the document as per your review comment. Does this benchmarking strategy looks fine? can i go ahead and get the benchmarking results using this strategy? |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: k82cn, Rajadeepan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Add Kubemark Benchmark Design Doc
Add Kubemark Benchmark Design Doc
Add Kubemark Benchmark Design Doc
What this PR does / why we need it:
This PR illustrates the Design Doc for kubemark Benchmark in Kube-Batch
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):#427
Special notes for your reviewer:
https://github.com/Rajadeepan/kube-batch/blob/doc/doc/design/Benchmark/kubemark/kubemark-benchmarking.md