The cache will not affect login, but will affect page rendering after logging in. To improve login performance you need to narrow the scope of the login query
On 5 January 2015 at 10:11, dennys <[email protected]> wrote: > I use Jenkins 1.580.2 and LDAP plugin 1.11. It works (authentication and > group), but the performance is not good. > It takes more then 10 seconds to login, and after enabling cache (size 500, > TTL 5mins), it's still the same. > > Does Jenkins write the cached data in any file or is there any solution to > confirm the cache is enabled or not? > > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/Could-I-know-the-LDAP-cache-is-enabled-or-not-tp4732888.html > Sent from the Jenkins users mailing list archive at Nabble.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/1420452666178-4732888.post%40n4.nabble.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMw%3Dj9ocTCPq2QbE8TZhLDpS8RXHCmdQ7ew1iWbM1GkOFg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
