Keycloak performance #14221

hnhai · 2022-09-06T12:41:46Z

hnhai
Sep 6, 2022

I'm install Keycloak 18.0.2 by Docker (Server 8 CPU, 16Gb ram) connect to PostgresDB in another Sever
LoadTest By Jmeter call to rest api of Keycloak to get Jwt token (1000 CCUs, duration: 3 minutes)
Keycloak used almost 8 core, response very slow. Start from miliseconds but increment to 30 seconds.
It is normal ? How I can fix it ? Thanks

hmlnarik · 2022-09-06T12:52:25Z

hmlnarik
Sep 6, 2022

Please provide more detailed description of your scenarios and deployment setup.

7 replies

hnhai Sep 7, 2022
Author

@hmlnarik

Which "API login" endpoint does the test call?
This API: /realms/realm_name/protocol/openid-connect/token

Do all the "1000 threads" hit the same single server at the same time?
Yes

hnhai Sep 8, 2022
Author

Hi @hmlnarik do you have any recomend ?

hmlnarik Sep 8, 2022

"Username and password" seems to point to resource owner grant flow. This is relies on hashing the passwords which is intentionally CPU-intensive, this requirement being independent of IAM implementation, Keycloak or other. However in real-world scenario, it is more likely that the users reuse their established sessions rather than reauthenticating with every request.
1000 simultaneous threads means lots of context switching (OS-dependent, Keycloak independent), and that applies to the load driver as well.
There was no mention of Keycloak being warmed up before the benchmark actually starts. Is there any warm-up time for JVM?

In total, I am afraid that the setup does not reflect realistic scenarios. Consider checking keycloak-benchmark project for assessing the resources needed to achieve the throughput for your requirements.

hnhai Sep 8, 2022
Author

@hmlnarik I got it. Thank for your help

nikhilmalhotra55 Jun 20, 2025

@hnhai how did you fix it ? facing the same problem. Around 350-400ms response time for raw api call on keycloak. same specs as yours.
I built a wrapper auth microservice which uses keycloak internally, but login api takes very long when using username, password based, token based api's are still fast.

Navigation Menu

Repository navigation

Keycloak performance #14221

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 7 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Keycloak performance #14221

Uh oh!

Uh oh!

hnhai Sep 6, 2022

Replies: 1 comment · 7 replies

Uh oh!

hmlnarik Sep 6, 2022

Uh oh!

hnhai Sep 7, 2022 Author

Uh oh!

hnhai Sep 8, 2022 Author

Uh oh!

hmlnarik Sep 8, 2022

Uh oh!

hnhai Sep 8, 2022 Author

Uh oh!

nikhilmalhotra55 Jun 20, 2025

hnhai
Sep 6, 2022

Replies: 1 comment 7 replies

hmlnarik
Sep 6, 2022

hnhai Sep 7, 2022
Author

hnhai Sep 8, 2022
Author

hnhai Sep 8, 2022
Author