Add simple stress test script (#12)

* Add simple stress test script

* Update with review comments

* Fix jar paths

* Fix jar paths in readme

* Review comments for linux support

Author: holly-cummins

README.md

@@ -47,3 +47,54 @@ There are some [scripts](scripts) available to help you run the application:
     - Runs a set of requests against a running application.
 - [`infra.sh`](scripts/infra.sh)
     - Starts/stops required infrastructure 
+
+## Running performance comparisons
+
+Of course you want to start generating some numbers and doing some comparisons, that's why you're here! 
+There are lots of *wrong* ways to run benchmarks, and running them reliably requires a controlled environment, strong automation, and multiple machines.
+Realistically, that kind of setup isn't always possible. 
+
+Here's a range of options, from easiest to best practice. 
+Remember that the easy setup will *not* be particularly accurate, but it does sidestep some of the worst pitfalls of casual benchmarking.
+
+
+### Quick and dirty: Single laptop, simple scripts
+
+Before we go any further, know that this kind of test is not going to be reliable. 
+Laptops usually have a number of other processes running on them, and modern laptop CPUs are subject to power management which can wildly skew results. 
+Often, some cores are 'fast' and some are 'slow', and without extra care, you don't know which core your test is running on. 
+Thermal management also means 'fast' jobs get throttled, while 'slow' jobs might run at their normal speed.
+
+Load shouldn't be generated on the same machine as the one running the workload, because the work of load generation can interfere with what's being measured. 
+
+But if you accept all that, and know these results should be treated with caution, here's our recommendation for the least-worst way of running a quick and dirty test. 
+We use [Hyperfoil](https://hyperfoil.io/https://hyperfoil.io/) instead of [wrk](https://github.com/wg/wrk), to avoid [coordinated omission](https://redhatperf.github.io/post/coordinated-omission/) issues. For simplicity, we use the [wrk2](https://github.com/giltene/wrk2) Hyperfoil bindings. 
+
+You can run these in any order. 
+
+```shell
+scripts/stress.sh quarkus3/target/quarkus-app/quarkus-run.jar
+scripts/stress.sh quarkus3-spring-compatibility/target/quarkus-app/quarkus-run.jar
+scripts/stress.sh springboot3/target/springboot3.jar
+```
+
+For each test, you should see output like 
+
+```shell
+  6001 requests in 30.002s,   4.84MB read
+Requests/sec: 200.02
+Transfer/sec: 165.29kB
+```
+### Acceptable: Run on a single machine, with solid automation and detailed output
+
+These scripts are being developed.
+
+### The best: Run tests in a controlled lab
+
+These tests are run on a regular schedule in Red Hat/IBM performance labs.
+The results are available in an internal [Horreum](https://github.com/Hyperfoil/Horreum) instance. 
+We are working on publishing these externally.
+
+
+
+

scripts/1strequest.sh

@@ -5,7 +5,7 @@
 
 # Example usage
 # 1) Run the Spring app 10 times
-# $ ./1strequest.sh "java -XX:ActiveProcessorCount=8 -Xms512m -Xmx512m -jar ../springboot3/target/app.jar" 10
+# $ ./1strequest.sh "java -XX:ActiveProcessorCount=8 -Xms512m -Xmx512m -jar ../springboot3/target/springboot3.jar" 10
 #
 # 2) Run the Quarkus app 10 times
 # $ ./1strequest.sh "java -XX:ActiveProcessorCount=8 -Xms512m -Xmx512m -jar ../quarkus3/target/quarkus-app/quarkus-run.jar" 10

scripts/infra.sh

@@ -1,6 +1,8 @@
 #!/bin/bash
 set -euo pipefail
 
+thisdir="$(realpath $(dirname "$0"))"
+
 help() {
   echo "This script starts the necessary services for the app in question"
   echo
@@ -19,7 +21,7 @@ exit_abnormal() {
 
 start_postgres() {
   echo "Starting PostgreSQL database '${DB_CONTAINER_NAME}'"
-  local pid=$(${engine} run -d --rm=true --name ${DB_CONTAINER_NAME} -v ./dbdata:/docker-entrypoint-initdb.d/ -p 5432:5432 -e POSTGRES_USER=fruits -e POSTGRES_PASSWORD=fruits -e POSTGRES_DB=fruits postgres:17 > /dev/null)
+  local pid=$(${engine} run -d --rm --name ${DB_CONTAINER_NAME} -v ${thisdir}/dbdata:/docker-entrypoint-initdb.d:O -p 5432:5432 -e POSTGRES_USER=fruits -e POSTGRES_PASSWORD=fruits -e POSTGRES_DB=fruits postgres:17)
   echo "PostgreSQL DB process: $pid"
 
   echo "Waiting for PostgreSQL to be ready..."

scripts/stress.sh

@@ -0,0 +1,14 @@
+#!/bin/bash
+
+thisdir=`dirname "$0"`
+
+# make sure the port is clear before enabling halting-on-error
+kill $(lsof -t -i:8080) &>/dev/null
+
+set -euo pipefail
+
+${thisdir}/infra.sh -s
+java -XX:ActiveProcessorCount=8 -Xms512m -Xmx512m -jar $1 &
+jbang wrk2@hyperfoil -t2 -c100 -d30s -R 200 --latency http://localhost:8080/fruits
+scripts/infra.sh -d
+kill $(lsof -t -i:8080) &>/dev/null