Vegeta Clients Configuration
The following variables are used in the examples in this section:
| $ipaddr | From the server, the IP Address of the application server's interface under test. |
| $app_port | From the server, the TCP port of the ATS application being run on the server. |
| $endpoint | The object or page that is tested on ATS. |
| $PATH | The ordered list of paths that Linux will search for executables when running a command |
| $pathtovegeta | The directory where Vegeta files are placed |
- Perform Vegeta build:
Example:
- Download Vegeta.
wget https://github.com/tsenart/vegeta/releases/download/v12.8.4/vegeta_12.8.4_linux_amd64.tar.gz - Untar Vegeta files.
tar xf vegeta_12.8.4_linux_amd64.tar.gz - Add Vegeta to environment variables
export PATH="${PATH}:${pathtovegeta}"
- Download Vegeta.
- Performance Vegeta benchmarking.
Vegeta is an open-source product used for benchmark HTTP/HTTPS. Tool has many different parameters to modify. For example, it allows you to specify the frequency of requests per second and connections that can be tested on the SUT. Additionally, it can be easily automated using scripts.
Measurements given by Vegeta are by default time to last byte.
Vegeta allows to test out many objects test case using targets parameter.
Note:Average latency is a measure of how fast SUT can respond Note:$ipaddr and $app_port are the same variables used in SUT configuration Example of Vegeta usage:
echo GEThttp://${ipaddr}:${app_port}/${endpoint} | ./vegeta attack -rate 100/s \ -insecure -duration 300s -timeout 10s -output /root/results.bin -connections 100 -keepalive \ -max-body=0 sleep 300s ./vegeta report -type json -output /root/results.json /root/results.bin