[
https://issues.jenkins-ci.org/browse/JENKINS-13945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sanga updated JENKINS-13945:
----------------------------
Description:
Version: 1.451
We switched from sun java to openjdk and noticed that copying artifacts from
master to slave took way longer than it had previously (x10 or more). Switching
back to sun java fixed the problem.
Related to this, the node ping times, as seen at: https://.../jenkins/computer/
were all up around 0.5s with openjdk and then when switching to sun java
dropped back down to where they should be (around 20ms).
If this is a bug in openjdk that's not really Jenkins problem, but perhaps
there's something in Jenkins to be done. Or at least it'd be beneficial for
Jenkins to know about this I guess.
was:
Version: 1.451
We switched from sun java to openjdk and noticed that copying artifacts from
master to slave took way longer than it had previously (x10 or more). Switching
back to sun java fixed the problem.
> Copy artifacts from master -> slaves takes about 10x longer with openjdk
> ------------------------------------------------------------------------
>
> Key: JENKINS-13945
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13945
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Environment: Debian 6
> Reporter: sanga
>
> Version: 1.451
> We switched from sun java to openjdk and noticed that copying artifacts from
> master to slave took way longer than it had previously (x10 or more).
> Switching back to sun java fixed the problem.
> Related to this, the node ping times, as seen at:
> https://.../jenkins/computer/ were all up around 0.5s with openjdk and then
> when switching to sun java dropped back down to where they should be (around
> 20ms).
> If this is a bug in openjdk that's not really Jenkins problem, but perhaps
> there's something in Jenkins to be done. Or at least it'd be beneficial for
> Jenkins to know about this I guess.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
