This repository contains a bunch of scripts you may use to conduct website load/stress testing. The scripts depend on a number of underlying tools so make sure you have them installed.
Using these scripts comes down to a simple workflow which is automated by having loadtest.sh calling the other scripts in sequence.
Before you begin testing, make sure you install the included siegerc file into your homedir's .siege/siege.conf file. The included install.sh script takes care of this step for you.
The installer also builds a parseresults binary if it isn't present yet. In order to dramatically speed up the interpretation of data, the parser was rewritten in extremely messy C++. If anyone here who actually DOES know what they're doing would refactor this montrosity, please feel free to do so!
For now, however, it does what I need it to do: import a bazillion lines of text into SQLite at good speed.
Make sure you have the following installed on your system before trying to build:
You might be able to use a precompiled binary from the binaries directory. Proceed at your own risk, though.
You need to install a number of packages before parseresults will compile:
dnf group install "C Development Tools and Libraries"
dnf install boost-devel boost-filesystem libstdc++-static sqlite-devel gnuplot siege wgetIn order to loadtest a website, run the loadtest.sh script followed by the hostname of the site or use the component scripts separately if you want more control over the process.
The spidering, running the test and parsing steps take a significant amount of time so make sure to plan accordingly.
The spider.sh script generates two files: urls.txt and urls_raw.txt. By default, the test runs against a clean set of URL's which are all verified to return HTTP status 200 at the time of spidering. This gives the most reliable test of the actual application working under the heaviest possible load. However, this isn't the most realistic simulation of the actual internet. When live, your website is likely to also receive requests which end up hitting redirects and error pages. Such URL's are included in the urls_raw.txt file. If you want to test this instead, you should run the test steps manually and replace urls.txt with urls_raw.txt right before you start the dotest.sh script.
Running stress tests on a website causes the server and its underlying infrastructure to be heavily used. Only run stress tests on systems you are explicitly authorized to test.