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

SystemCredentialsProvider causing slowness in jenkins UI

      We are facing extreme slowness in production environment and when we tried to deep dive for the cause we figured out that "com.cloudbees.plugins.credentials.SystemCredentialsProvider.getStore(SystemCredentialsProvider.java:350)" Executed method is taking elapsed time of "240,939". And this happens whenever we tried to navigate any folder , jobs and system configuration, credential options. Also whenever we are planning to add and delete jenkins credential store it is taking nearly 5 mins to complete the operation. Even adding and deletion of credentials via pipeline is taking more time.

          [JENKINS-73810] SystemCredentialsProvider causing slowness in jenkins UI

          Mark Waite added a comment -

          You'll need to provide much more information before others will be able to help you. Please refer to "How to report an issue" for the types of details that are needed.

          Mark Waite added a comment - You'll need to provide much more information before others will be able to help you. Please refer to "How to report an issue" for the types of details that are needed.

          Markus Winter added a comment - - edited

          Seems someone modified the ticket

          Markus Winter added a comment - - edited Seems someone modified the ticket

          Pari added a comment -

          We contacted cloud bees, they helped us to identify the root cause. They installed the support bundle plugin on jenkins and took the support dump and analyzed it. Finally they figured that in Manage Jenkins -> System -> Job Config History was installed and "Do not save duplicate history" was enabled which was causing the slowness. Hence they recommended us to disable it then it worked. Now we are not experiencing any slowness in jenkins. May be based on this bug you guys can analyze why this option is causing the slowness in jenkins. 

          Pari added a comment - We contacted cloud bees, they helped us to identify the root cause. They installed the support bundle plugin on jenkins and took the support dump and analyzed it. Finally they figured that in Manage Jenkins -> System -> Job Config History was installed and "Do not save duplicate history" was enabled which was causing the slowness. Hence they recommended us to disable it then it worked. Now we are not experiencing any slowness in jenkins. May be based on this bug you guys can analyze why this option is causing the slowness in jenkins. 

          Mark Waite added a comment -

          Thanks for letting us know, pari0592!

          Mark Waite added a comment - Thanks for letting us know, pari0592 !

          Pari added a comment -

          Anytime for the community !!.. I'm interested to see when this bug gets prioritized and fixed. Please let me know any changes needed to modify this bug so it's aligned with your scrum standards. 

          Pari added a comment - Anytime for the community !!.. I'm interested to see when this bug gets prioritized and fixed. Please let me know any changes needed to modify this bug so it's aligned with your scrum standards. 

          Mark Waite added a comment -

          There really isn't a scrum for the job config history plugin or any scrum standards. Jenkins plugins are fixed by Jenkins plugin maintainers when they choose to fix them. If you can provide a minimal case that duplicates the problem, it is much more likely that a plugin maintainer will be interested. If you can provide a pull request with a fix for the issue, it is even more likely that the issue will be fixed.

          Mark Waite added a comment - There really isn't a scrum for the job config history plugin or any scrum standards. Jenkins plugins are fixed by Jenkins plugin maintainers when they choose to fix them. If you can provide a minimal case that duplicates the problem, it is much more likely that a plugin maintainer will be interested. If you can provide a pull request with a fix for the issue, it is even more likely that the issue will be fixed.

            Unassigned Unassigned
            pari0592 Pari
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: