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

feat/perf-test: update README and broker-imc benchmark #4607

Merged
merged 2 commits into from
Dec 8, 2020

Conversation

zhongduo
Copy link
Contributor

Fixes #4599

Proposed Changes

  • Update README to use perf-eventing namespace
  • Update benchmark configuration

@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Nov 27, 2020
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 27, 2020
@knative-prow-robot knative-prow-robot added the area/test-and-release Test infrastructure, tests or release label Nov 27, 2020
@codecov
Copy link

codecov bot commented Nov 27, 2020

Codecov Report

Merging #4607 (b084909) into master (ad755bd) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #4607   +/-   ##
=======================================
  Coverage   81.31%   81.31%           
=======================================
  Files         290      290           
  Lines        8176     8176           
=======================================
  Hits         6648     6648           
  Misses       1128     1128           
  Partials      400      400           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ad755bd...5f07679. Read the comment docs.

test/performance/README.md Outdated Show resolved Hide resolved
test/performance/README.md Outdated Show resolved Hide resolved
configured with a single benchmark.
1. Create a namespace `perf-eventing` if not exists. To use a different
namespace, pleaes replace all the namespaces in
all bash commands and yaml configuration files with your choice.

1. Install Knative eventing by following the steps in
https://github.com/knative/eventing/blob/2c6bf0526634804b7ebeee686445901440cc8edd/test/performance/performance-tests.sh#L31
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it still relevant to recommend following this script which is not up-to-date?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, I personally didn't check this at all. I simply install knative eventing myself. Should we just change it to "install Knative eventing and components under test such as MT broker"?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that would be a good idea, and link to DEVELOPMENT.md

1. Retrieve results from mako-stub using the script in
[knative/pkg](https://github.com/knative/pkg/blob/master/test/mako/stub-sidecar/read_results.sh):
[knative/pkg](https://github.com/knative/pkg/blob/master/test/mako/stub-sidecar/read_results.sh)
where `pod_name` is the name of the aggreator pod:

```
bash "$GOPATH/src/knative.dev/pkg/test/mako/stub-sidecar/read_results.sh" "$pod_name" perf-eventing ${mako_port:-10001} ${timeout:-120} ${retries:-100} ${retries_interval:-10} "$output_file"
Copy link
Contributor

Choose a reason for hiding this comment

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

Since we are vendoring the mako stub, this path should be adjusted to the eventing vendor subdirectory.

@tommyreddad
Copy link
Contributor

/assign

@google-cla
Copy link

google-cla bot commented Nov 27, 2020

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no Indicates the PR's author has not signed the CLA. and removed cla: yes Indicates the PR's author has signed the CLA. labels Nov 27, 2020
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla
Copy link

google-cla bot commented Nov 27, 2020

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: yes Indicates the PR's author has signed the CLA. and removed cla: no Indicates the PR's author has not signed the CLA. labels Nov 27, 2020
@google-cla
Copy link

google-cla bot commented Nov 27, 2020

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@tommyreddad
Copy link
Contributor

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 27, 2020
configured with a single benchmark.
1. Create a namespace `perf-eventing` if not exists. To use a different
namespace, please replace all the namespaces in
all bash commands and yaml configuration files with your choice.
Copy link
Contributor

Choose a reason for hiding this comment

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

do u mean bash scripts here or is commands intended?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Command is commonly used to refer to one line script.

@tayarani
Copy link
Contributor

Some minor comments I'll leave up to you.

/lgtm

@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Nov 30, 2020
@google-cla
Copy link

google-cla bot commented Nov 30, 2020

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@tayarani
Copy link
Contributor

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 30, 2020
@zhongduo
Copy link
Contributor Author

zhongduo commented Dec 2, 2020

/assign @slinkydeveloper

@slinkydeveloper
Copy link
Contributor

/lgtm

not sure about the meaning of mako stuff, looping @grantr for the final approval

@zhongduo
Copy link
Contributor Author

zhongduo commented Dec 2, 2020

@chizhg might have the context.

@zhongduo
Copy link
Contributor Author

zhongduo commented Dec 4, 2020

/assign @chizhg

@chizhg
Copy link
Member

chizhg commented Dec 8, 2020

/approve

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chizhg, zhongduo

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 8, 2020
@knative-prow-robot knative-prow-robot merged commit ca2def5 into knative:master Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test-and-release Test infrastructure, tests or release cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Broken performance test
7 participants