https://github.com/rojosinalma/web_benchmark_tool
Benchmark whatever website/endpoint/etc using Apache Benchmark and GnuPlot for results
https://github.com/rojosinalma/web_benchmark_tool
Last synced: 3 months ago
JSON representation
Benchmark whatever website/endpoint/etc using Apache Benchmark and GnuPlot for results
- Host: GitHub
- URL: https://github.com/rojosinalma/web_benchmark_tool
- Owner: rojosinalma
- Created: 2016-09-08T14:13:59.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2016-09-08T14:27:36.000Z (almost 9 years ago)
- Last Synced: 2025-03-01T05:52:58.355Z (3 months ago)
- Language: Shell
- Homepage:
- Size: 3.91 KB
- Stars: 0
- Watchers: 0
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# load_test
_Run a load test using Apache Benchmark against whatever you want._
### IMPORTANT
#### **DO NOT RUN THIS AGAINST PRODUCTION**
**...or at least not without letting your closest DevOps know first...**
_...and even so, expect him to probably say "NO" anyway..._
---
### Requirements:
* [Apache Benchmark 2.3+](https://httpd.apache.org/docs/2.4/programs/ab.html)
* [Gnuplot](http://www.gnuplot.info/)
### Usage:
TODO: Use short/long opts and run more than one bench at the same time.
```bash
$ ./run_benchmarks.sh
```
* The plotted graphs can be found inside the `plots` folder.
* For more details check inside each benchmark's `output` folder.
* All outputted files are named with this structure `_date('%d%m%Y')_time(%H%M%S)`
This way you can pair plotted results with their according outputs.
* In case you want to clean all your results, you can run `scripts/delete_results.sh`.
---
### Add new benchmarks:
1. **Folder structure:**
```
base_dir/
├───benchmarks/
├─────
├───────output/
├───────benchmark.sh
├───────plot.p
├───plots/
├───scripts/
├───run_benchmarks.sh
```
The `benchmarks` folder contains all your custom benchmarks, inside it you should create:
The `output` folder contains everything the `benchmark.sh` script creates as output (logfiles, csv, gnuplot logs, etc...).
The `benchmark.sh` file contains all the logic to the benchmark itself **without the plotting**. (Don't forget to chmod it for execution).
The `plot.p` is a gnuplot file which contains the configuration that gnuplot must follow for creating the images.
3. **Plots Folder:**
Contains graphs from the benchmark plotted with GnuPlot.
3. **Scripts Folder:**
The `run_single_benchmark.sh` acts as a wrapper for all the steps of the benchmark (The actual benchmark and plotting the graph).
It takes `` name as a parameter. **You should not need to call this file, unless you know what you're doing.**
Additionally there's a `delete_results.sh` script that will clean all contents of all `output` and `plots`.
3. **Main script:**
The `run_benchmarks.sh` script acts as a wrapper for all benchmarks and allows the user to define the **total amount of requests**, **concurrency** and call more than one benchmark.