Repository navigation
How to optimize Keycloak to handle a lot of groups #42238
Unanswered
RaduNicolaeEduard
asked this question in
Q&A
Replies: 1 comment
|
I’m also running into similar challenges with Keycloak when dealing with a very large number of groups. In my case, operations like retrieving groups by path are noticeably slowing down as the group count grows, and sometimes the requests even fail when querying through the Python Keycloak library. This is starting to impact performance in our application. Any advice, tuning tips, or best practices for handling such a large and continuously growing group set in Keycloak would be greatly appreciated. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We currently have over 20,000 groups in Keycloak, and this number is expected to continue growing. We’ve observed that certain operations are becoming slower as the group list increases in size.
In particular, our application makes frequent calls to the get group by path endpoint.
As the number of groups grows, these requests are taking significantly longer to process, which is starting to impact overall performance.
What optimizations or best practices are recommended to ensure Keycloak can efficiently handle a large and continuously growing number of groups?
Keycloak version 24All reactions