Huge performance degradation on job rename

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: core
    • Environment:
      Jenkins version 2.235.1 (but we have similar behavior on multiple versions)
      We are using Jenkins in docker container on Ubuntu Host.

      We experience a huge performance hit after job rename for 30 minutes. The Jenkins is unresponsive and unusable from user side. Loading of any Jenkins page took 4-5 minutes.

       

      Is it possible: 

       - Option1 - to lower the priority of the thread responsible for the search and replace of the old job name with the new one in the old builds

       - Option2 - to implement an additional group with permissions to rename jobs

       - Option3 - to add an option to disable search and replace the old job name with the new job name in all older jobs builds (different than the one which we rename)

       

      Please let me know if there is already plan for fixing this issue? 

            Assignee:
            Unassigned
            Reporter:
            Plamen Angelov
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: