Thomas, this test is run with whatever local database Keycloak defaults to. We're using Postgres generally, and we will have more information pertaining to tests against Postgres soon.

Stian, thanks for the tips. I am currently running a test to ingest about 50m users into the default database with the user cache disabled, 8gb mem (Xmx and Xms), and parallel GC threads == processor count.

Though my test is young (430k users ingested), I'm noticing memory allocation increasing in lockstep with the number of ingested users. Is it expected to continue in this fashion, or is Keycloak designed to level off in its memory usage?

On Tue, Jun 21, 2016 at 4:29 PM Stian Thorgersen <sthorger@redhat.com> wrote:

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_cache.html#d4e3187

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@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 and opened an issue here 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

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user