Last active
May 29, 2017 07:43
-
-
Save goncalotomas/8a1d7754d608b4ae40b80a05382a5071 to your computer and use it in GitHub Desktop.
How to run a local FMKe benchmark without an antidote docker image
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/bin/bash | |
| echo "running small benchmark with antidote..." | |
| # TODO insert command to start up antidote | |
| # or start antidote prior to running this script | |
| # NOTE remember to use a fresh antidote build (no stored data). | |
| # Use 'make relclean' to wipe saved data from antidote | |
| # this script assumes that you have an antidote node reachable at 'antidote@127.0.0.1' | |
| ./scripts/start_fmke.sh | |
| # Fill database with testdata: | |
| echo "populating antidote via FMKe..." | |
| ./scripts/populate_fmke_travis.erl 1 'fmk@127.0.0.1' | |
| # Start benchmark | |
| echo "starting benchmark..." | |
| _build/default/lib/basho_bench/_build/default/bin/basho_bench config/fmke_travis.config | |
| if [ -s tests/current/error.log ]; then | |
| # start existing docker container: | |
| echo "fatal: benchmark exited prematurely with errors" | |
| exit 3 | |
| fi | |
| echo "benchmark complete." | |
| ./scripts/stop_fmke.sh | |
| # TODO insert command to terminate antidote after this benchmark | |
| # or terminate it manually after the script. | |
| # NOTE: between benchmarks, antidote data should be removed by running 'make relclean' | |
| echo "done" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment