Keycloak by default caches users in-memory, by default it will keep up to
10000 entries cached. You can verify that there's no leak by disabling the
user cache provider. See
http://keycloak.github.io/docs/userguide/keycloak-server/html/server_cach...
If you're planning on having millions of users I suggest you increase the
allocated memory for the JVM (512MB which it seems you have is not
sufficient).
On 22 June 2016 at 00:29, Chris Hairfield <chairfield(a)gmail.com> wrote:
Hello,
When testing Keycloak 1.9.8 by ingesting a few million users, we find that
Keycloak leaks memory until it is rendered unresponsive (see graph).
Increasing JVM memory only increases the time it takes to encounter this
issue.
We have put together a test project here
<
https://github.com/anaerobic/keycloak-leakage> and opened an issue here
<
https://issues.jboss.org/browse/KEYCLOAK-3146> as we continue to
investigate. As we are relying on Keycloak as a central infrastructural
component, any help would be greatly appreciated.
We'll update with more information as we find it.
Thanks,
Chris
[image: mem-cpu.png]
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user