[JIRA] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls

Fri, 15 Nov 2013 15:32:40 -0800

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.

Reply via email to