Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14837

ldap email seems to perform a bind operation for each and every id that needs to be resolved

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • ldapemail-plugin
    • None
    • Jenkins ver. 1.447.1.1 (Jenkins Enterprise by CloudBees 12.05)
      LDAP Email plugin ver 0.7

      I noticed that the ldap email resolver seems to perform a bind operation before resolving each and every email id. I think this slows down the email resolution a lot. Is is possible to cache that info and reuse the bind info - at least for the current job (or thread) that is requesting email resolution. I think that should greatly improve the performance.

          [JENKINS-14837] ldap email seems to perform a bind operation for each and every id that needs to be resolved

          Jose Sa added a comment -

          Maybe this is not specific just to ldap email plugin as using the ldap authentication also allows to resolve email from username.

          We had one instance that there were so commiters since last failed build that a build that normally took 5 minutes was taking more than 20 because of constructing notification list from ldap.

          Mail information don't change that often, if they would be stored in the user information cached for at least a week it would greatly improve this.

          Jose Sa added a comment - Maybe this is not specific just to ldap email plugin as using the ldap authentication also allows to resolve email from username. We had one instance that there were so commiters since last failed build that a build that normally took 5 minutes was taking more than 20 because of constructing notification list from ldap. Mail information don't change that often, if they would be stored in the user information cached for at least a week it would greatly improve this.

            justinedelson justinedelson
            dpanchal Deepak Panchal
            Votes:
            5 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: