The damn deploy repository of the Divide and map. Now. has been refactored. And that’s a great opportunity for another round of load testing.
This is the third round of load testing, see the first and the second one if you are interested.
The load testing is a bit different from the last time. I performed load testing of new, freshly deployed damn project instance on $6/month VPS with 1 GB RAM, single 2.5 GHz vCPU, and 25 GB SSD. (The changes from the last time are that there is no more load testing of the “production” server, the price increased by $1/month, and shared_buffers is now 256 MB instead of 409 MB.)
The preparation for load testing on the server’s side, when the damn project is deployed, is just to run
docker-compose -f damn-deploy/gen.yml run --rm prepareloadtest
to create 1000 test users and 10 (load) testing areas in the database. For each run of load testing, the database has been deleted and created again with
systemctl stop damn-http.service
reboot
docker volume rm damn-deploy_damndb-volume
systemctl start damn.target
docker-compose -f damn-deploy/gen.yml run --rm prepareloadtest
commands. For each run of load testing, log the server’s utilization with
sar -o load-test-100 -A 15 $((4 * 61)) 1>/dev/null 2>&1
Then, from that file, you can generate data series and plot the graphs with
./get-info.sh 100
gnuplot plot1.pl
gnuplot plot2.pl
where the content of the corresponding files is
get-info.sh:



