[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Title: Message Title Carl van Schaik commented on JENKINS-18276 Re: Archiving artifacts from a slave node is extremely slow even with 1.509.1+ With Linux slaves our builds generate large artifacts (up to 2.3 GB after compressed with XZ). Copying these from and to builds takes a while obviously, the main reason seems to be that Jenkins archives via its control channel (e.g. ssh slave - using java SSH implementation JSCH). The java ssh just can't get anywhere near 1Gb/s network speed that native SSH can manage easily. I don't think this plugin will ever be able to provide suitable speeds without a major redesign to support alternative copy methods - e.g. using native SCP, SSL etc where supported by the slave/master. If going to the effort, I would highly recommend also separating the master node from the archive storage node - e.g. we started with Jenkins in a small VM, it now requires one with 300+ of GB of storage and can only manage the last 48 hours of artifacts. Delta-compression is useless for us as well, it works on only a certain type of data. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Title: Message Title Carl van Schaik edited a comment on JENKINS-18276 Re: Archiving artifacts from a slave node is extremely slow even with 1.509.1+ With Linux slaves our builds generate generates large artifacts ( up to 2.3 GB 2GB+ after compressed with XZ). Copying these from and to builds takes a while obviously, the main reason seems to be that Jenkins archives via its control channel (e.g. ssh slave - using java SSH implementation JSCH). The java ssh just can't get anywhere near 1Gb/s network speed that native SSH can manage easily.I don't think this plugin will ever be able to provide suitable speeds without a major redesign to support alternative copy methods - e.g. using native SCP, SSL etc where supported by the slave/master. If going to the effort, I would highly recommend also separating the master node from the archive storage node - e.g. we started with Jenkins in a small VM, it now requires one with 300+ of GB of storage and can only manage the last 48 hours of artifacts.Delta-compression is useless for us as well, it works on only a certain type of data. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Title: Message Title Lars Lykke commented on JENKINS-18276 Re: Archiving artifacts from a slave node is extremely slow even with 1.509.1+ I've introduced a zip/unzip step in our build proces, which has HALVED the time used spent on check-out and compile. Our steps consists of check-out and archiving og 11500 files (approx. 350 MB) and subsequent compilation in a separate job. By zipping files prior to archiving and the unzipping after copying artifacts we've managed to reduce time spent checking out and compiling from 10 min (check-out/archiving/fingerprinting) + 30 min (copying, compiling, archiving) to 4 min + approx. 15 min. I don't know if this is Windows specific but it might be relevant to make it an option of the copy-artifacts and archiving functionality that it should support zipping through check-boxes to reduce the amount of steps involved? I've used powershell to zip and unzip the files in between the jobs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Title: Message Title Lars Lykke commented on JENKINS-18276 Re: Archiving artifacts from a slave node is extremely slow even with 1.509.1+ I just upgraded to 1.638 with a Win7 master and Win2012 slaves connected through JNLP. The slaves are running Jenkins as a Windows service. All machines run as virtual machines with non-dedicated disks. However, I would still assume the Network speed to be the bottleneck no matter what? If I archive artifacts (3,95 GB) from my build job it takes approx. 15 min 30 sec. = 4.32 MBps. The artifacts consist of approx. 4100 files. Copying artifacts from the master node (778MB) takes approx 8 min 50 sec. =1.47 MBps. The artifacts copied consisted of approx. 2.770 files. I've not made elaborate statistical sampling but the above is more less the normal time for copying artifacts. If I take a project with few files, I get 350 MB transferred in 17 sec. resulting in 20.6 MBps. So the slow transfer times in my case seems related to the transfer of many small files whereas transferring a few large files seem to go sufficiently fast. Would it make sense to zip artifacts prior to archiving? That sort of goes against the 'copy artifacts' step where it's possible to select/deselect files based on pattern? I don't assume this would be possible if I zip all the files prior to archiving. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Title: Message Title Daniel Beck commented on JENKINS-18276 Re: Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Does this issue still occur on recent Jenkins versions? If so, what kind of slave (SSH, JNLP, …) is affected? I think there was a performance fix a few months ago… Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Title: Message Title Edgars B. commented on JENKINS-18276 Re: Archiving artifacts from a slave node is extremely slow even with 1.509.1+ I do not even know where to start. On our build machines (similar setup) Jenkins has just finished a build and has been sitting there doing absolutely nothing for the last 1h, so I looked up the issue online. Hope for improvements. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Lars Lykke commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ I'm seeing the same issue with Jenkins v. 1.581 (Master, Windows 7). My slaves are Windows 7/Windows 2012 machines with jenkins running as a service on them. Retrieving artifacts from upstream job takes a very long time (approx. 7 min for 750 MB ~ 100MB/min). The slaves are connected using JNLP agent Archiving artifacts is about the same: 12 min. for 2 GB. How can I provide additional information which might help in resolving this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
rggjan commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Same problem here, happens for a linux jenkins with a Mac OS X slave. Archiving ~100MB of data takes 10 minutes, while copying it manually over the network only takes around 10 econds... Jenkins ver. 1.565.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Akihiro KAYAMA commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Total 11GB artifacts copy takes 30 minutes from Windows slave to Linux master. There is another critical bug https://issues.jenkins-ci.org/browse/JENKINS-10629 also. I decided copy artifacts directly to $JENKINS_HOME/jobs/$JOB_NAME/builds/$BUILD_ID/archive/. create public directory in Windows slave allowing anonymous read access kick network copy shell script using smbclient on Linux master from Windows batch script via ssh(putty's plink) 11GB copy using smbclient takes only 3 minutes. Archive directories in matrix project has more complicated path so bothersome but possible too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Akihiro KAYAMA edited a comment on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Total 11GB artifacts copy takes 30 minutes from Windows slave to Linux master. There is another critical bug https://issues.jenkins-ci.org/browse/JENKINS-10629 also. I decided copy artifacts directly to $JENKINS_HOME/jobs/$JOB_NAME/builds/$BUILD_ID/archive/. create public directory in Windows slave allowing anonymous read access kick network copy shell script using smbclient on Linux master from Windows batch script via ssh(putty's plink) 11GB copy using smbclient takes only 3 minutes. Archive directories in matrix project has more complicated path so bothersome but possible too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Ninian commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ We're seeing this issue too, on 1.554.2. Unix slaves can archive artifacts quickly, but it takes a factor of about 10 times greater to upload the artifacts from windows slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
tq rst commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Same problem on 1.565. Master is linux, slave is Windows jnlp. Unlike what Marcel Beister reported, there is a transfer going on throughout the whole time for us. It's just extremely slow (250kB/s instead of 100mB/s). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Michael Hashimoto commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Still reproducible on Jenkins ver. 1.537 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Marcel Beister commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ We found the problem. Although the log file showed "archiving artifacts", jenkins was waiting for the previous concurrent build to finish. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Marcel Beister commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ 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? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Christian Höltje commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Same problem with Jenkins 1.509.2 and Copy Artifacts 1.27 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Jakub Štiller commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Jakub Štiller commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Marcin Zajączkowski created JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Jun/13 4:27 PM Description: 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. Environment: Jenkins 1.515, CentOS 6 64-bit, Java 7 (Oracle) Project: Jenkins Priority: Major Reporter: Marcin Zajączkowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
