-
Notifications
You must be signed in to change notification settings - Fork 93
Release notes for v0.2 + doc update #100
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
Changes from 4 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,13 +25,13 @@ For building the Nighthawk test server, see [here](source/server/README.md). | |
| ### Test it | ||
|
|
||
| ```bash | ||
| bazel test -c dbg //test:nighthawk_test | ||
| bazel test -c dbg //test/... //integration/... | ||
| ``` | ||
|
|
||
| ### Build it | ||
|
|
||
| ```bash | ||
| bazel build -c opt //:nighthawk_client | ||
| bazel build -c opt //:nighthawk_client nighthawk_test_server nighthawk_service | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does this work? Don't the latest binaries need a path? Also, should we just have a filegroup or something for this?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes this works. I will look into creating a filegroup. |
||
| ``` | ||
|
|
||
| ### Using the CLI | ||
|
|
@@ -155,6 +155,40 @@ Where: | |
|
|
||
| ``` | ||
|
|
||
| ### Nighthawk gRPC service | ||
|
|
||
| The gRPC service can be used to start a server which is able to perform back-to-back benchmark runs upon request. The service interface definition [can be found here.](https://github.com/envoyproxy/nighthawk/blob/59a37568783272a6438b5697277d4e56aa16ebbe/api/client/service.proto) | ||
|
|
||
|
|
||
| ```bash | ||
| ➜ bazel-bin/nighthawk_service --help | ||
|
|
||
| USAGE: | ||
|
|
||
| bazel-bin/nighthawk_service [--listen <address:port>] [--] [--version] | ||
| [-h] | ||
|
|
||
|
|
||
| Where: | ||
|
|
||
| --listen <address:port> | ||
| The address:port on which the Nighthawk gRPC service should listen. | ||
| Default: 0.0.0.0:8443. | ||
|
|
||
| --, --ignore_rest | ||
| Ignores the rest of the labeled arguments following this flag. | ||
|
|
||
| --version | ||
| Displays version information and exits. | ||
|
|
||
| -h, --help | ||
| Displays usage information and exits. | ||
|
|
||
|
|
||
| L7 (HTTP/HTTPS/HTTP2) performance characterization tool. | ||
|
|
||
| ``` | ||
|
|
||
| ## A sample benchmark run | ||
|
|
||
| ```bash | ||
|
|
||
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.
Can we move integration underneath test? It seems cleaner to have all tests in a single tree?
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.
That is where they lived at first, but it caused problems with the coverage test:
https://circleci.com/gh/envoyproxy/nighthawk/1193?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
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.
Can you update to use the new LLVM-style coverage script? See envoyproxy/envoy#7552. This might not fix it, but it makes coverage much faster and easier to debug :)