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

change benchmark notebook name #111

Merged
merged 1 commit into from
Mar 7, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/benchmarking.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,14 +26,14 @@ This test will illustrate the maximum number of requests that can be pushed thro

We will use cordened off kubernetes nodes running locust so the latency from node to node prediction calls on GCP will also be part of the returned statistics.

A [notebook](https://github.com/SeldonIO/seldon-core/blob/master/notebooks/kubectl_demo_gcp_loadtest.ipynb) provides the end to end test for reproducability.
A [notebook](https://github.com/SeldonIO/seldon-core/blob/master/notebooks/benchmark_simple_model.ipynb) provides the end to end test for reproducability.

We use:

* 1 replica of the stub model running on 1 n1-standard-16 GCP node
* We use 3 nodes to run 64 locust slaves with a total of 256 clients calling as fast as they can.

See [notebook](https://github.com/SeldonIO/seldon-core/blob/master/notebooks/kubectl_demo_gcp_loadtest.ipynb) for details.
See [notebook](https://github.com/SeldonIO/seldon-core/blob/master/notebooks/benchmark_simple_model.ipynb) for details.

### REST Results

Expand Down