[JIRA] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon commented on JENKINS-20534 Pegged CPU by writeSymlink calls Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/jenkins/model/PeepholePermalink.java http://jenkins-ci.org/commit/jenkins/f768fb7aed02bf4e944eff10cb2ba3007d98e560 Log: JENKINS-20534 Avoid usage of temporary file to write symlink. Creating a symlink is an atomic operation, and additionally usage of tmp file + rename performs very badly on NTFS file system because of the way the rename is tracked in the $MFT. In case symbolic links are not supported, we still fallback to a regular file. (cherry picked from commit c0742b8bff9fe407e568da7ed860f30d9ea8aedc) 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-20534) Pegged CPU by writeSymlink calls
dogfood commented on JENKINS-20534 Pegged CPU by writeSymlink calls Integrated in jenkins_main_trunk #3192 JENKINS-20534 Avoid usage of temporary file to write symlink. (Revision c0742b8bff9fe407e568da7ed860f30d9ea8aedc) [FIXED JENKINS-20534] Noting merge of #1057. (Revision 5c83c64e7af95bc5f216d841e4257c79403931d8) Result = SUCCESS Vincent Latombe : c0742b8bff9fe407e568da7ed860f30d9ea8aedc Files : core/src/main/java/jenkins/model/PeepholePermalink.java Jesse Glick : 5c83c64e7af95bc5f216d841e4257c79403931d8 Files : changelog.html 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-20534) Pegged CPU by writeSymlink calls
Oleg Nenashev commented on JENKINS-20534 Pegged CPU by writeSymlink calls Marked the issue as lts-candidate 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-20534) Pegged CPU by writeSymlink calls
Oleg Nenashev updated JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Oleg Nenashev (10/Feb/14 7:43 PM) Labels: lts-candidate performance 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-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon resolved JENKINS-20534 as Fixed Pegged CPU by writeSymlink calls Change By: SCM/JIRA link daemon (10/Feb/14 5:45 PM) Status: In Progress Resolved Resolution: Fixed 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-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon commented on JENKINS-20534 Pegged CPU by writeSymlink calls Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/jenkins/model/PeepholePermalink.java http://jenkins-ci.org/commit/jenkins/c0742b8bff9fe407e568da7ed860f30d9ea8aedc Log: JENKINS-20534 Avoid usage of temporary file to write symlink. Creating a symlink is an atomic operation, and additionally usage of tmp file + rename performs very badly on NTFS file system because of the way the rename is tracked in the $MFT. In case symbolic links are not supported, we still fallback to a regular file. 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-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon commented on JENKINS-20534 Pegged CPU by writeSymlink calls Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/5c83c64e7af95bc5f216d841e4257c79403931d8 Log: [FIXED JENKINS-20534] Noting merge of #1057. Compare: https://github.com/jenkinsci/jenkins/compare/da8eba20babf...5c83c64e7af9 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-20534) Pegged CPU by writeSymlink calls
Jesse Glick assigned JENKINS-20534 to Vincent Latombe Pegged CPU by writeSymlink calls Change By: Jesse Glick (10/Feb/14 4:20 PM) Assignee: Vincent Latombe 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-20534) Pegged CPU by writeSymlink calls
Jesse Glick started work on JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Jesse Glick (10/Feb/14 4:20 PM) Status: Open In Progress 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-20534) Pegged CPU by writeSymlink calls
Vincent Latombe commented on JENKINS-20534 Pegged CPU by writeSymlink calls PR to avoid renaming of symlinks https://github.com/jenkinsci/jenkins/pull/1057 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-20534) Pegged CPU by writeSymlink calls
Jesse Glick updated JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Jesse Glick (13/Dec/13 3:38 PM) Labels: performance 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-20534) Pegged CPU by writeSymlink calls
Jesse Glick updated JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Jesse Glick (13/Dec/13 3:39 PM) URL: https://github.com/jenkinsci/jenkins/pull/1057 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-20534) Pegged CPU by writeSymlink calls
Vincent Latombe updated JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Vincent Latombe (12/Nov/13 11:14 AM) Attachment: JENKINS-20534_threaddump.txt 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-20534) Pegged CPU by writeSymlink calls
Vincent Latombe created JENKINS-20534 Pegged CPU by writeSymlink calls Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Nov/13 11:13 AM Description: I'm getting cpu stuck at 100% when a lot of executor threads are updating permalinks Environment: Jenkins 1.532 + backports to stable Project: Jenkins Priority: Critical Reporter: Vincent Latombe 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-20534) Pegged CPU by writeSymlink calls
Vincent Latombe commented on JENKINS-20534 Pegged CPU by writeSymlink calls A significant number of threads seem to take time during rename of the cache file. Corresponding disk queues don't seem stressed at all, it only have a CPU impact. java.lang.Thread.State: RUNNABLE at java.io.WinNTFileSystem.rename0(Native Method) at java.io.Win32FileSystem.rename(Win32FileSystem.java:535) at java.io.File.renameTo(File.java:1391) at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:185) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:142) at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:219) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.maven.MavenBuild$ProxyImpl2.end(MavenBuild.java:574) 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-20534) Pegged CPU by writeSymlink calls
Vincent Latombe edited a comment on JENKINS-20534 Pegged CPU by writeSymlink calls A significant number of threads seem to take time during rename of the cache file. Corresponding disk queues don't seem stressed at all, it only has a CPU impact. java.lang.Thread.State: RUNNABLE at java.io.WinNTFileSystem.rename0(Native Method) at java.io.Win32FileSystem.rename(Win32FileSystem.java:535) at java.io.File.renameTo(File.java:1391) at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:185) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:142) at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:219) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.maven.MavenBuild$ProxyImpl2.end(MavenBuild.java:574) 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-20534) Pegged CPU by writeSymlink calls
Vincent Latombe updated JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Vincent Latombe (12/Nov/13 12:30 PM) Environment: Jenkins 1.532 + backports to stable Windows Server 2008 R2 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.
