Skip to content

Commit d22c0e1

Browse files
howardjohnmandarjog
authored andcommitted
Cleanup perf/README (#84)
I forgot to delete some stuff that was moved to istio-install/README
1 parent c78e12c commit d22c0e1

File tree

1 file changed

+0
-28
lines changed

1 file changed

+0
-28
lines changed

perf/README.md

-28
Original file line numberDiff line numberDiff line change
@@ -10,31 +10,3 @@ This folder contains tests for performance and stability. There are different ty
1010
The intent of these tests is to be run continuously for extend periods of time, which differentiates them from integration tests.
1111
1. [/benchmark](./benchmark) provides a test to measure the latency and metrics of traffic between pods in various setups.
1212
1. [/load](./load) provides tools to generate large services to test Istio under heavy load.
13-
14-
15-
## Setup Istio
16-
17-
For performance testing, it is recommended to setup Istio with performance oriented values, but it is not required.
18-
19-
### Setup With Performance Parameters
20-
21-
Look at values.yaml for details.
22-
23-
To setup Istio, run `DNS_DOMAIN=your-example-domain ./setup_istio.sh release-1.1-20190125-09-16`.
24-
25-
To just output the deployment file, run `DRY_RUN=1 DNS_DOMAIN=your-example-domain ./setup.sh release-1.1-20190125-09-16`.
26-
27-
You may replace the release in the command to the release to test.
28-
29-
You may also override the Helm repo or release URL:
30-
31-
```bash
32-
export HELMREPO_URL=https://storage.googleapis.com/istio-release/releases/1.1.0-rc.0/charts/index.yaml
33-
export RELEASE_URL=https://github.com/istio/istio/releases/download/untagged-c41cff3404b8cc79a97e/istio-1.1.0-rc.0-linux.tar.gz
34-
35-
DNS_DOMAIN=your-example-domain ./setup.sh release-1.1-20190203-09-16
36-
```
37-
38-
### Setup With Custom Installation
39-
40-
The performance tests can also run on an existing Istio installation. This can be useful to test out settings or modifications to Istio.

0 commit comments

Comments
 (0)