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

Jenkins.getUser(...) is debilitatingly slow with a large number of users

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
      None
    • Environment:
      1.554.1 with JENKINS-22822
    • Similar Issues:

      Description

      We've got 1026 users on builds.apache.org, and when you try to view a user or go through a user's views, etc, load time is abominable most of the time - ~54 seconds or so in the example below. While we're seeing a lot of what might be i/o related slowness in other areas, this seems kind of insane. Does User.getAll() really need to reload every user's config.xml every 10 seconds?

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I'd guess that JENKINS-47429 solves this issue. It has been released in 2.89.3.

            Andrew Bayer please confirm

            Show
            oleg_nenashev Oleg Nenashev added a comment - I'd guess that JENKINS-47429 solves this issue. It has been released in 2.89.3. Andrew Bayer please confirm
            Hide
            batmat Baptiste Mathus added a comment - - edited

            At least the style used between Andrew and Sam Van Oort seems to confirm this is the same issue:
            "debilitatingly slow" and "Absolutely atrocious performance" look like perfect duplicates to me .

            Show
            batmat Baptiste Mathus added a comment - - edited At least the style used between Andrew and Sam Van Oort seems to confirm this is the same issue: "debilitatingly slow" and "Absolutely atrocious performance" look like perfect duplicates to me .
            Hide
            svanoort Sam Van Oort added a comment -

            The user caching behavior has been tweaked a couple times a couple different ways, so I think the variant here can either be closed as no longer applicable or a dupe (doing it now). 

            Show
            svanoort Sam Van Oort added a comment - The user caching behavior has been tweaked a couple times a couple different ways, so I think the variant here can either be closed as no longer applicable or a dupe (doing it now). 
            Hide
            abayer Andrew Bayer added a comment -

            Yeah, sounds fine to me.

            Show
            abayer Andrew Bayer added a comment - Yeah, sounds fine to me.
            Hide
            svanoort Sam Van Oort added a comment - - edited

            Baptiste Mathus Other choice phrasings "user lookup is slower than molasses in winter" and "I like to watch paint dry while fetching changelog entries for a large branch."

            Show
            svanoort Sam Van Oort added a comment - - edited Baptiste Mathus  Other choice phrasings "user lookup is slower than molasses in winter" and "I like to watch paint dry while fetching changelog entries for a large branch."

              People

              • Assignee:
                Unassigned
                Reporter:
                abayer Andrew Bayer
              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: