-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add refresh token phase to AuthorizationCode scenario #434
Conversation
benchmark/src/main/scala/keycloak/scenario/KeycloakScenarioBuilder.scala
Outdated
Show resolved
Hide resolved
@ddurham2 I am currently testing this locally, do you think anything else is left on this PR before we can take this forward and move it from Draft status to Ready for review ? Also made some minor changes to make the code little bit more explicit. |
Yes, I'm still tweaking it locally. I'm both doing tests and adjusting KC and adjusting the tests as I go. I did get it up to 100k on a local minikube deployment. I still need to figure out how to specify some of the testing parameters which are new for this test, I think. |
@@ -29,7 +29,7 @@ DIRNAME=$(dirname "$RESOLVED_NAME") | |||
|
|||
# Default values | |||
JAVA_OPTS="-server" | |||
JAVA_OPTS="${JAVA_OPTS} -Xmx1G -XX:+HeapDumpOnOutOfMemoryError" | |||
JAVA_OPTS="${JAVA_OPTS} -Xmx4G -XX:+HeapDumpOnOutOfMemoryError" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw the gatling java process up in the 3.5GB range when ramping up to 100k users
benchmark/src/main/scala/keycloak/scenario/CommonSimulation.scala
Outdated
Show resolved
Hide resolved
benchmark/src/main/scala/keycloak/scenario/CommonSimulation.scala
Outdated
Show resolved
Hide resolved
…s during the scenario share connections using --refresh-token-period instead of --user-think-time for delay between refreshes
… default it does the same things but without a refresh
…ilder.scala method
@ahus1 - I did the test with both minikube and openshift and also with the ec2 load runners and local benchmark, things looked good to me. do you want to give this a last look, before I merge it ? |
Thanks guys. Much appreciated! |
refresh token load test scenario
resolves #416