The default hashing iterations is fairly high to safeguard for the case of
a leaked database.
See:
http://www.keycloak.org/docs/latest/server_admin/topics/threat/password-d...
If you are comfortable with decreasing the number of iterations that's
definitely the first thing to try to increase performance.
On Oct 12, 2017 18:53, "Thelo" <thelo.gaultier(a)gmail.com> wrote:
Hi,
As we are currently load testing Keycloak to see whether it could be a good
fit in our system, we experience trouble to reach good performance for the
user login.
In our current set up we do direct login via password against Keycloak and
we get around 30 user logins per second.
Here is our current set up:
- 4 instances of Keycloak ( 1 CPU / 800MB of memory each, running in
Kubernetes)
- 1 Postgres db in AWS RDS with 20GB of SSD storage, 2 vCPU and 8GB of
memory
As it is hard to believe that one instance can only handle 10 requests per
second we were wondering if someone had done similar tests and if you would
be willing to share the results / test configuration .
Many thanks,
Thelo
--
Sent from:
http://keycloak-user.88327.x6.nabble.com/
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user