Task List Performance with several hundred users

[camunda-community-hub]

Task List Performance with several hundred users

[VonDerBeck]

Hi @jomu78,
I have seen the usage of the plugin with arround 50.000 users at one of my own customers. The administration frontend performed very well for that. Of course listing all users took some time (not extremely bad, but noticeably long). When using a filter the performance was really great again. This is true for the Camunda Admin frontend.
As the Camunda Task List is often used in POC's and showcases only, the performance of the Task List has not been in focus till now.

There is no possibility to cache the users and groups within the Identity Provider. And I don't think this makes sense either. Caching / Syncing with LDAP is the job of Keycloak itself.
The more interesting question for the Keycloak Identity Provider is, if really all users need to show up in Camunda or if we need to introduce some kind of filter for Camunda relevant users, e.g. users of a specified subset of "BPM" groups.

So my question to you is: in your scenario - how many of the LDAP users are relevant for your BPM tasks and processes?

[VonDerBeck]

Your performance problems might as well be caused by a bad Keycloak configuration. Please check the storage mode of the LDAP user federation. See https://www.keycloak.org/docs/10.0/server_admin/#storage-mode

[jomu78]

@VonDerBeck: thanks for the hints. I will check the LDAP and Keycloak configuration.

[VonDerBeck]

Hi @jomu78,

is this still an open issue for you after checking the config of your LDAP user federation? Currently I'm not able to reproduce this issue. I have no problems with Camunda Tasklist and serveral 1000 users.

[jomu78]

Hi @VonDerBeck ,

sorry for the late response, I did not had the time to update here.
We finally found the reason why. Basically the LDAP connection pool was not working as expected because settings were ovewritten from other LDAP setup. See https://groups.google.com/forum/#!topic/keycloak-dev/p1PxK8ZfnB0 and https://groups.google.com/forum/#!topic/keycloak-user/YaJgFkdfnl0 for more details.

But this is an Keycloak issue and not related to the camunda plugin - so closing this one here.