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