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

Archiving artifacts from a slave node is extremely slow even with 1.509.1+

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • Jenkins 1.515, CentOS 6 64-bit, Java 7 (Oracle)

      I see no changes in a speed of archiving artifacts after upgrade to 1.515 (with slave upgraded to 2.23) which should have applied fix from JENKINS-7813.
      43MB WAR archives in 102 seconds vs. <2 seconds with SCP. No one confirmed on the mailing list that was able to get significant change after upgrade. It was suggested to open the new issue.

          [JENKINS-18276] Archiving artifacts from a slave node is extremely slow even with 1.509.1+

          Marcin Zajączkowski created issue -
          Marcin Zajączkowski made changes -
          Link New: This issue is related to JENKINS-7813 [ JENKINS-7813 ]

          Jakub Štiller added a comment -

          I can confirm it. When copy 150MB WAR using scp the copy speed is 30MB/s, when archiving by Jenkins the rate is only about 3MB/s. I have tried steps described in JENKINS-3922 but no success. Running Jenkins v1.513 with slave v2.23.

          Jakub Štiller added a comment - I can confirm it. When copy 150MB WAR using scp the copy speed is 30MB/s, when archiving by Jenkins the rate is only about 3MB/s. I have tried steps described in JENKINS-3922 but no success. Running Jenkins v1.513 with slave v2.23.

          Jakub Štiller added a comment -

          We found that problem is not only copy of artifacts. Also upload artifacts to Nexus via Deploy Artifacts to Maven repository is slow only 3MB/s. When setup job on slave to run mvn deploy the upload speed is 30MB/s. So something must be wrong with master server. The master runs on Tomcat 6.0.36.

          I have also look at Jenkins sources and what I understand that uploading artifacts is done via Maven native API, so I think that there should be no differences when calling maven in build and in artifacts upload on master.

          Do you have any hints, where the problem may be? We are looking on tomcat, java, OS setup. But no luck yet.

          Jakub Štiller added a comment - We found that problem is not only copy of artifacts. Also upload artifacts to Nexus via Deploy Artifacts to Maven repository is slow only 3MB/s. When setup job on slave to run mvn deploy the upload speed is 30MB/s. So something must be wrong with master server. The master runs on Tomcat 6.0.36. I have also look at Jenkins sources and what I understand that uploading artifacts is done via Maven native API, so I think that there should be no differences when calling maven in build and in artifacts upload on master. Do you have any hints, where the problem may be? We are looking on tomcat, java, OS setup. But no luck yet.

          Christian Höltje added a comment -

          Same problem with Jenkins 1.509.2 and Copy Artifacts 1.27

          Christian Höltje added a comment - Same problem with Jenkins 1.509.2 and Copy Artifacts 1.27

          Sebastian Laag added a comment -

          Same problem with LTS 1.509.2

          Sebastian Laag added a comment - Same problem with LTS 1.509.2

          Guillaume Boucherie added a comment -

          Same problem with LTS 1.509.3

          Guillaume Boucherie added a comment - Same problem with LTS 1.509.3

          jeremy ladron added a comment -

          Same problem on LTS 1.509.3, any workaround for this major issue ? (avoiding a downgrade...)

          jeremy ladron added a comment - Same problem on LTS 1.509.3, any workaround for this major issue ? (avoiding a downgrade...)

          Josh Chappelle added a comment -

          Same problem on 1.517. The slave machine is windows xp.

          Josh Chappelle added a comment - Same problem on 1.517. The slave machine is windows xp.

          Marcel Beister added a comment -

          We have some jobs that require archiving less than 1 MB of artifacts (with 1.535 on Windows 7 Slave), but they are stuck in "archiving artifacts" for HOURS!! Other projects produce much bigger artifact but get the job done significantly faster.

          Does the archiving somehow depend on the number of files in the workspace or the size of the workspace?

          Marcel Beister added a comment - We have some jobs that require archiving less than 1 MB of artifacts (with 1.535 on Windows 7 Slave), but they are stuck in "archiving artifacts" for HOURS!! Other projects produce much bigger artifact but get the job done significantly faster. Does the archiving somehow depend on the number of files in the workspace or the size of the workspace?

            Unassigned Unassigned
            emszpak Marcin Zajączkowski
            Votes:
            36 Vote for this issue
            Watchers:
            43 Start watching this issue

              Created:
              Updated: