You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: create a keycloak 24 benchmark image (#426)
* chore: create a keycloak 24 benchmark image
* chore: update benchmark test documentation
* chore: point the benchmark builder back at 26
* chore: add 4th test to docs
* chore: add 4th test to docs
Copy file name to clipboardExpand all lines: benchmark/README.md
+24-4Lines changed: 24 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
- You need a keycloak server with dataset provider added to be able to use it for generating test data
8
8
- To build such server image, run `.github/workflows/publish-image-keycloak-benchmark.yml` that builds an image using `docker/keycloak/Dockerfile-26-perf` that explicitly copies `docker/keycloak/dataset-providers/keycloak-benchmark-dataset-0.15-SNAPSHOT.jar` provider
9
-
- Deploy keycloak server run from this image **ONLY** in a test namespace
9
+
- Deploy keycloak server run from this image **ONLY** in a test namespace. See the [sso-helm-charts repo](https://github.com/bcgov/sso-helm-charts/tree/main/charts/keycloak).
10
10
- After the testing is complete, uninstall the server from the namespace
11
11
12
12
### Runner Image
@@ -66,7 +66,6 @@ export ADMIN_PASSWORD=
66
66
# using 100 users and 100 clients to make 34 req/s for a duration of upto 30 mins
- Create `.env` from `.env.example` and set the appropriate values for the variables
@@ -79,12 +78,33 @@ export ADMIN_PASSWORD=
79
78
- Run `make cleanup` to ensure old resources get deleted
80
79
- Run `make run_job` to deploy a secret and a job that executes `entrypoint.sh` script in a pod
81
80
81
+
## ADDITIONAL_CONFIG
82
+
83
+
There are four runs we have done with the previous versions of keycloak. In order for runs to be comparable the same runs should be done on future versions. These are controlled by the `ADDITIONAL_CONFIG` env var.
- The html report will be generated under the `./results` directory if running locally without using `entrypoint.sh`
85
105
- Running `entrypoint.sh` locally or in a pod would send the report via email to the email address set under `RECEPIENT` environment variable
86
-
- Download the attachment from the email and use `base64 --decode` to decode the file
87
-
- After the decode, you can extract the contents from the archive
106
+
- Download the attachment from the email and use `base64 --decode` to decode the file`base64 --decode results.tar.gz>decoded_results.tar.gz`
107
+
- After the decode, you can extract the contents from the archive and use the browser to preview them `file://<<PATH_TO_FILE>>/req_browser-to-log---<<TIMESTAMP>>.html`
0 commit comments