Archiving artifacts takes 9 hours

[David Hreczany-2]

Hi Jenkins users,

I am experiencing a problem with my Jenkins in that the archiving artifacts portion of the build is taking way too long; 9 hours to be exact.

 

I am running Jenkins 1.412. All my slaves are on a virtual machine as well as my master Jenkins.

 

I have 113 jobs and the artifacts being archived are only 250MB.

 

My Jenkins threadDump for the machine experiencing the problem is showing a lot of threads being blocked on java.io.PrintStream, java.util.logging.ConsoleHandler, and hudson.plugins.logparser.LogParserReader.

 

I have one thread that is waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer.

 

Does anyone have any thoughts on how to speed up the “Archiving artifacts” portion of my build.

 

Thanks very much.

 

 

Dave

David Hreczany

Lead Quality Assurance Engineer

 

 

Office 312 948 5400

 

 

NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by or to any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail and destroy this email retaining no electronic or printed copies.

 

[Sami Tikka]

My Jenkins was archiving very slowly when I was using OpenJDK 1.6. When I changed to Sun JDK 1.6, the archiving sped up a lot. 

-- Sami

David Hreczany <[hidden email]> kirjoitti 20.8.2012 kello 16.57:

Hi Jenkins users,

I am experiencing a problem with my Jenkins in that the archiving artifacts portion of the build is taking way too long; 9 hours to be exact.

 

I am running Jenkins 1.412. All my slaves are on a virtual machine as well as my master Jenkins.

 

I have 113 jobs and the artifacts being archived are only 250MB.

 

My Jenkins threadDump for the machine experiencing the problem is showing a lot of threads being blocked on java.io.PrintStream, java.util.logging.ConsoleHandler, and hudson.plugins.logparser.LogParserReader.

 

I have one thread that is waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer.

 

Does anyone have any thoughts on how to speed up the “Archiving artifacts” portion of my build.

 

Thanks very much.

 

 

Dave

David Hreczany

Lead Quality Assurance Engineer

<image001.jpg>

 

 

Office 312 948 5400

 

<image002.jpg>

 

NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by or to any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail and destroy this email retaining no electronic or printed copies.

 

[David Karlsen]

There is issues in jira for it - and a workaround:

https://issues.jenkins-ci.org/browse/JENKINS-3922

2012/8/20 David Hreczany <[hidden email]>

Hi Jenkins users,

I am experiencing a problem with my Jenkins in that the archiving artifacts portion of the build is taking way too long; 9 hours to be exact.

 

I am running Jenkins 1.412. All my slaves are on a virtual machine as well as my master Jenkins.

 

I have 113 jobs and the artifacts being archived are only 250MB.

 

My Jenkins threadDump for the machine experiencing the problem is showing a lot of threads being blocked on java.io.PrintStream, java.util.logging.ConsoleHandler, and hudson.plugins.logparser.LogParserReader.

 

I have one thread that is waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer.

 

Does anyone have any thoughts on how to speed up the “Archiving artifacts” portion of my build.

 

Thanks very much.

 

 

Dave

David Hreczany

Lead Quality Assurance Engineer

 

 

Office 312 948 5400

 

 

NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by or to any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail and destroy this email retaining no electronic or printed copies.

 

--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen