• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Solaris/x86, cluster of 5 nodes, all machines in cluster are identical

      Clone workspace performance is poor. Whilst compilation takes around 4 minutes, archiving the workspace afterwards takes the total job time out to 35 minutes! Similarly un-archiving it at the start of downstream jobs.

      We have 4 steps, Compile, quick test, package, full test.
      Compile uses Perforce SCM, we use clone workspace after that to ensure downstream builds use identical files but other compiles can continue in parallel. So we need almost the files in the entire workspace.
      The filesystem workspace size is about 1.6Gb
      The archived workspace.zip file size is about 1.4Gb

      An "exclude" filter may help a little but I think there is something slow going on.
      Note that we use slaves as well so the piped data may have an impact, but all the machines are very close together.
      When the compile runs on the master node it doesn't seem any quicker.

          [JENKINS-10520] clone-workspace-scm performance is poor

          Ed Randall created issue -
          OHTAKE Tomohiro made changes -
          Link New: This issue is duplicated by JENKINS-10519 [ JENKINS-10519 ]
          Ed Randall made changes -
          Attachment New: clone-workspace [ 21645 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 140713 ] New: JNJira + In-Review [ 175332 ]
          Andrew Bayer made changes -
          Assignee Original: Andrew Bayer [ abayer ]
          Jenkins IRC Bot made changes -
          Component/s New: clone-workspace-scm-plugin [ 16060 ]
          Component/s Original: clone-workspace-plugin [ 15700 ]

            Unassigned Unassigned
            edrandall Ed Randall
            Votes:
            13 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: