diff options
author | Alexander Polcyn <apolcyn@google.com> | 2018-07-25 18:04:27 -0700 |
---|---|---|
committer | Alexander Polcyn <apolcyn@google.com> | 2018-07-26 10:45:12 -0700 |
commit | a2160f547f3f89232caf0d7541da6ed3b1095a59 (patch) | |
tree | 9e81320bdc69ec64fae82944e2e32804ebcd8880 /tools/run_tests/performance | |
parent | ae8d3efc3a360b289f0b33e1c53c8c73960cb31f (diff) |
Wait a configurable amount of time for benchmark channels to become ready
Diffstat (limited to 'tools/run_tests/performance')
-rw-r--r-- | tools/run_tests/performance/README.md | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/tools/run_tests/performance/README.md b/tools/run_tests/performance/README.md index 2fc1a27c9b..791270ab38 100644 --- a/tools/run_tests/performance/README.md +++ b/tools/run_tests/performance/README.md @@ -104,3 +104,31 @@ Example memory profile of grpc-go server, with `go tools pprof`: ``` $ go tool pprof --text --alloc_space http://localhost:<pprof_port>/debug/heap ``` + +### Configuration environment variables: + +* QPS_WORKER_CHANNEL_CONNECT_TIMEOUT + + Consuming process: qps_worker + + Type: integer (number of seconds) + + This can be used to configure the amount of time that benchmark + clients wait for channels to the benchmark server to become ready. + This is useful in certain benchmark environments in which the + server can take a long time to become ready. Note: if setting + this to a high value, then the scenario config under test should + probably also have a large "warmup_seconds". + +* QPS_WORKERS + + Consuming process: qps_json_driver + + Type: comma separated list of host:port + + Set this to a comma separated list of QPS worker processes/machines. + Each scenario in a scenario config has specifies a certain number + of servers, `num_servers`, and the driver will start + "benchmark servers"'s on the first `num_server` `host:port` pairs in + the comma separated list. The rest will be told to run as clients + against the benchmark server. |