keycloak-scim/testsuite/performance
2014-06-19 10:19:10 +01:00
..
src/test model refactor for caching 2014-06-10 18:50:08 -04:00
pom.xml Bumped version to 1.0-beta-4-SNAPSHOT 2014-06-19 10:19:10 +01:00
README.md Basic fix of performance tests and added README. Still requires work... 2014-05-30 11:03:16 +02:00

Configuration of performance test

  • At this moment it's src/test/jmeter/keycloak_perf_test.jmx where you can configure among other things: -- "ThreadGroup.num_threads" -- number of worker threads -- "LoopController.loops" -- Number of loops per each thread.

  • src/test/jmeter/system.properties -- System properties including configuration of providers. Allow to specify: -- which model to use -- which test to run -- configuration of individual tests. Properties for each test documented in the file

Running performance tests

cd KEYCLOAK_HOME/testsuite mvn clean install -DskipTests=true -Pperformance-tests

Results:

  • Log is in: testsuite/performance/target/jmeter/logs/keycloak_perf_test.jmx.log
  • More charts and reports are inside: testsuite/performance/target/jmeter/results/

Example for running test

Run: mvn clean install -DskipTests=true -Pperformance-tests with OOTB configuration (Assumption is mongo running on 27017 as it's using mongo by default). This will create 10 new realms.

Then change keycloak_perf_test.jmx to have "ThreadGroup.num_threads" to 10 and "LoopController.loops" to 100 And change "keycloak.perf.workerClass" to "org.keycloak.testsuite.performance.CreateUsersWorker" in system.properties

Then run again: mvn clean install -DskipTests=true -Pperformance-tests This will create 1000 new users (10 worker threads and each worker doing 100 iterations. Each worker is creating users in separate realm)

TODO: Easier configuration without need to edit config files, more user friendly, easier to configure and run test