There are too many job in queue, which makes using Jenkins.getInstance().getQueue().schedule2 take a long time.

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

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor
    • Component/s: core
    • Environment:
      use jenkins docker images, and version is 2.361.4-lts-jdk11.

      There are too many job in queue，and Simultaneously trigger a large number of jobs, which makes using Jenkins.getInstance().getQueue().schedule2 take a long time. When i see the code in hudson.model.Queue.schedule2 and scheduleInternal, and i find the lock That is ReentrantLock is used in three times. Is there a better way to optimize hudson.model.Queue.schedule2 to help us improve concurrency performance?

            Assignee:
            Unassigned
            Reporter:
            tom
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: