Hi, we are planning to do some more work to reduce the performance issues we see when using the AD plugin. The first step is what we did in the AD plugin itself, as seen here: https://github.com/jenkinsci/active-directory-plugin/pull/6 This is the second step, since we still see performance issues in the UI.
Right now, there are a lot of unnecessary computations involved in answering whether a user has a permission. Through profiling we have seen that these computations, when using the AD plugin, is what is giving us our slow UI performance. The changes would be in the hudson.security package of Jenkins core and would consist of caching the permissions given to a specific user so that calls to ACL.hasPermission ( of which there are ALOT in our system ) can give cached values as answers. We plan to add a user cache that would be invalidated when the user logs out and in as well as invalidating group caches when the general config in Jenkins is saved. Does anyone see any problems with our reasoning or should we go forward with this? Br Tomas Westling, Sony Mobile Communications AB -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
