This test will test the performance of processing models to the RDF4J repository materialiser
The test will send 10,000 members to ldi-orchestrator, the orchestrator will process and send the members to the RDF4J repository
Note: if needed, copy the environment file (.env) to a personal file (e.g.
user.env
) and change the settings as needed. If you do, you need to add--env-file user.env
to eachdocker compose
command. NOTE for Windows users:
Use this tutorial
to run JMeter in the docker-compose file. You can use DISPLAY=host.docker.internal:0.0 as environment variable to skip the ipconfig step.
Prerequisites:
-
Pull the latest version of the ldi orchestrator
docker pull ghcr.io/informatievlaanderen/ldi-orchestrator:latest
-
Prepare directory that will contain the results
mkdir tests/results chmod 777 tests/results rm -rf tests/results/output rm -rf tests/results/report.jtl
-
Start test POST 10k members to LDIO to materialise to the RDF4J repository
export BATCH_SIZE=500 docker compose up
-
End test
docker compose down
-
Test results
To run the different tests, repeat step 1 -> 3 above and insert the results below.
- Test run: February 23, 2023
- Docker image
- ldi-orchestrator: ghcr.io/informatievlaanderen/ldi-orchestrator:
- Resources for both the orchestrator as server:
deploy: resources: limits: cpus: '4' memory: '2GB' reservations: cpus: '2' memory: '1GB'
ldes/ldi-orchestrator:2.0.0-SNAPSHOT
Following error was counted 230 times, or for sample it has received:
Non HTTP response code: java.net.SocketTimeoutException/Non HTTP response message: Read timed out
-
ghcr.io/informatievlaanderen/ldi-orchestrator:20240311160234
-
Last run on: March 11th 2024
-
OS: Windows 11 Enterprise v 22H2
-
Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz 2.42 GHz
-
Installed RAM: 32.0 GM
10,000 members were sent to the ldio workbench in 10 different threads, which all have a life span of 45 seconds, in the table below, you can see how members were successfully posted to the workbench for some batch sizes and how many members were processed per second
Batch Size | Members successfully posted | Members processed per second |
---|---|---|
50 | 10000 | 269.45 |
100 | 10000 | 345.77 |
250 | 10000 | 350.14 |
500 | 10000 | 406.77 |
1000 | 10000 | 425.17 |