• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • Fedora 10 x86_64 Master, Win7 32bit Slave

      We are running 1.380. I can watch a 300MB tarball get transferred to the Hudson master slowly over 30+ minutes. An scp between the same machines and same files/directories takes less than 3 minutes.

          [JENKINS-7813] Archiving artifacts very slow

          Tom Fanning added a comment -

          Thank you very much! Look forward to seeing this in a release.

          Tom Fanning added a comment - Thank you very much! Look forward to seeing this in a release.

          David Karlsen added a comment -

          Yes - hope it will be backported into the LTS real soon

          David Karlsen added a comment - Yes - hope it will be backported into the LTS real soon

          pancake added a comment -

          FYI: updating SSH Slaves plugin to 0.23 resulted in problem described in JENKINS-17388 for us.

          pancake added a comment - FYI: updating SSH Slaves plugin to 0.23 resulted in problem described in JENKINS-17388 for us.

          @pancake: you do know that the warning is just a warning and not an actual problem. It was just some debugging code and when it is printed it means that you will not see the performance improvements but otherwise everything will be fine. i.e. cosmetic

          Stephen Connolly added a comment - @pancake: you do know that the warning is just a warning and not an actual problem. It was just some debugging code and when it is printed it means that you will not see the performance improvements but otherwise everything will be fine. i.e. cosmetic

          pancake added a comment -

          @stephenconnolly: thanks!
          What do we need to upgrade to get those performance improvements? Is it Jenkins itself? Will the optimization be merged into LTS? Is there a way to find out such thing ourselves (from GitHug Commit History?) instead of bothering developers?

          pancake added a comment - @stephenconnolly: thanks! What do we need to upgrade to get those performance improvements? Is it Jenkins itself? Will the optimization be merged into LTS? Is there a way to find out such thing ourselves (from GitHug Commit History?) instead of bothering developers?

          Jesse Glick added a comment -

          @tomfanning, @davidkarlsen2, @pancake: as http://jenkins-ci.org/changelog notes, these changes are in Jenkins 1.509. That will be the basis of the next LTS.

          Jesse Glick added a comment - @tomfanning, @davidkarlsen2, @pancake: as http://jenkins-ci.org/changelog notes, these changes are in Jenkins 1.509. That will be the basis of the next LTS.

          I see no changes after upgrade to 1.515 (with slave upgraded to 2.23). 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.

          Marcin Zajączkowski added a comment - I see no changes after upgrade to 1.515 (with slave upgraded to 2.23). 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.

          Jesse Glick added a comment -

          @emszpak: reclosing since the intended fixes were delivered. There may be other as-yet-undiagnosed problems slowing down your connection; someone would need to reproduce the issue, file separately (can use JIRA links), and analyze it.

          Jesse Glick added a comment - @emszpak: reclosing since the intended fixes were delivered. There may be other as-yet-undiagnosed problems slowing down your connection; someone would need to reproduce the issue, file separately (can use JIRA links), and analyze it.

          Sven Amann added a comment -

          Not sure about the connection, but same symptoms.

          Sven Amann added a comment - Not sure about the connection, but same symptoms.

          Stephane Odul added a comment -

          I can confirm the same issue. The files take 10s to publish to our maven repo at the end of the build but before that they take over 4m to publish back to the master. I initially blamed a slow VM as the existing master but after upgrading to fresh hardware today and switching from CentOS to Ubuntu 12.04 we are still getting the issue. We are running Jenkins 1.527 with Java 1.7.0_17 (not open jdk).

          Stephane Odul added a comment - I can confirm the same issue. The files take 10s to publish to our maven repo at the end of the build but before that they take over 4m to publish back to the master. I initially blamed a slow VM as the existing master but after upgrading to fresh hardware today and switching from CentOS to Ubuntu 12.04 we are still getting the issue. We are running Jenkins 1.527 with Java 1.7.0_17 (not open jdk).

            Unassigned Unassigned
            gtuhl gtuhl
            Votes:
            40 Vote for this issue
            Watchers:
            46 Start watching this issue

              Created:
              Updated:
              Resolved: