1 a.m.
Hi Stian,
Thank you for your reply.
The new tokens needs to be generated for each user, which is needed from security point of
view. The performance tests were also conducted using single Admin user and token for
admin user; however in that case the performance was not good. In between 15th to 20th
admin token access requests – the CPU usage of keycloak Java process was crossing 90 to
120% mark.
As you have mentioned, Creating tokes are expected to be a bit CPU intensive – what should
be the server configuration in terms of CPU to deal with more than 500 users to use
keycloak as OAuth provider.
Thanks, Vaibhav
From: Stian Thorgersen [mailto:sthorger@redhat.com]
Sent: Thursday, May 19, 2016 6:28 PM
To: Vaibhav Naldurgkar
Cc: keycloak-user(a)lists.jboss.org
Subject: Re: [keycloak-user] Keycloak OAuth High CPU usage
Creating tokes are expected to be a bit CPU intensive as they need to be signed. When you
say you try to generate tokens for 10-20 users are you doing performance tests and having
10-20 threads generating tokens? It shouldn't make any difference if you have 10 or if
you have 200 users, it's the total number of tokens that can be generated that's
an issue. Having 200 concurrent users with a access token timeout of 60 seconds should
mean that you need to be able to generate roughly 200/60 tokens = 3.3 tokens/sec.
On 19 May 2016 at 13:24, Vaibhav Naldurgkar
<vaibhav_naldurgkar@persistent.com<mailto:vaibhav_naldurgkar@persistent.com>>
wrote:
Hi All,
I am using Keycloak 1.9.3 with default configuration. Keycloak server is installed on RHEL
6.5 virtual image with 4 CPU , 8 GB RAM and java version is jdk1.8.0_73 We are trying to
use keycloak as a OAuth provider. But when we try and generate
token(http:///auth/realms/master/protocol/openid-connect/token<http://auth/realms/master/protocol/openid-connect/token>)
for more than 10-20 users the server gets too slow and cpu usage goes over 100%.
Any pointers on how to improve performance of keycloak OAuth provider. We need to support
at least 200 concurrent users.
Thanks, Vaibhav
DISCLAIMER ========== This e-mail may contain privileged and confidential information
which is the property of Persistent Systems Ltd. It is intended only for the use of the
individual or entity to which it is addressed. If you are not the intended recipient, you
are not authorized to read, retain, copy, print, distribute or use this message. If you
have received this communication in error, please notify the sender and delete all copies
of this message. Persistent Systems Ltd. does not accept any liability for virus infected
mails.
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-user
DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of
Persistent Systems Ltd. It is intended only for the use of the individual or entity to
which it is addressed. If you are not the intended recipient, you are not authorized to
read, retain, copy, print, distribute or use this message. If you have received this
communication in error, please notify the sender and delete all copies of this message.
Persistent Systems Ltd. does not accept any liability for virus infected mails.