James Phillips
13d9476a43
|
8 years ago | |
---|---|---|
.. | ||
conf | bench: Fixing benchmark address on some systems | 11 years ago |
Makefile | Gets benchmarks running again and does a rough pass for 0.7.1. | 8 years ago |
README.md | Gets benchmarks running again and does a rough pass for 0.7.1. | 8 years ago |
bench-aws.json | Fix Consul download link in benchmark scripts | 9 years ago |
bench.json | Gets benchmarks running again and does a rough pass for 0.7.1. | 8 years ago |
results-0.2.md | bench: results for 0.3rc | 11 years ago |
results-0.3.md | bench: results for 0.3rc | 11 years ago |
results-0.7.1.md | Gets benchmarks running again and does a rough pass for 0.7.1. | 8 years ago |
results-0.7.1.svg | Gets benchmarks running again and does a rough pass for 0.7.1. | 8 years ago |
README.md
Consul Benchmark
This repo contains the automation necessary for the Consul benchmarks.
There is a single main Packer file bench.json
. To use it, the variables
for do_client_id
and do_api_key
must be provided. These correspond to
your DigitalOcean client ID and API key.
When Packer runs, it will generate 3 images:
- bench-bootstrap - Consul server in bootstrap mode
- bench-server - Consul server
- bench-worker - Worker node
For the benchmark you should start 1 bootstrap instance, and 2 normal servers. As many workers as desired can be started. Once the nodes are up, you must SSH into one of the Consul servers.
Connect all the nodes with:
$ consul join <n1> ... <n5>
This will connect all the nodes within the same datacenter.
To run the benchmarks, use the Makefile:
$ cd /
$ make # Runs all the benchmarks
$ make put # Runs only the PUT benchmarks
There is no good way to currently cause multiple workers to run at the same time, so I just type in the make command and rapidly start the test on all workers. It is not perfect, but the test runs long enough that the calls overlap.