-
Notifications
You must be signed in to change notification settings - Fork 593
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
Conversation
1dd84e3
to
acbddc5
Compare
Codecov Report
@@ 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.
|
test/performance/README.md
Outdated
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 |
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.
Is it still relevant to recommend following this script which is not up-to-date?
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.
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"?
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 think that would be a good idea, and link to DEVELOPMENT.md
test/performance/README.md
Outdated
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" |
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.
Since we are vendoring the mako stub, this path should be adjusted to the eventing vendor subdirectory.
/assign |
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. ℹ️ Googlers: Go here for more info. |
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. ℹ️ Googlers: Go here for more info. |
3c4f9ec
to
60c1987
Compare
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
60c1987
to
4627c8a
Compare
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
/lgtm |
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. |
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.
do u mean bash scripts here or is commands intended?
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.
Command is commonly used to refer to one line script.
Some minor comments I'll leave up to you. /lgtm |
4627c8a
to
5f07679
Compare
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
/lgtm |
/assign @slinkydeveloper |
/lgtm not sure about the meaning of mako stuff, looping @grantr for the final approval |
@chizhg might have the context. |
/assign @chizhg |
/approve |
[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 |
Fixes #4599
Proposed Changes
perf-eventing
namespace