|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
OK, I made a little investigation.
It seems that serialization/de-serialisation in https://github.com/jenkinsci/jacoco-plugin/blob/master/src/main/java/hudson/plugins/jacoco/ExecutionFileLoader.java
takes a lot of cpu, also load doesn't not spread evenly on all cores (I used htop).
In our case I'm speaking about ovirt project (~3800 classes).
iftop doesn't shows significant network traffic and iostat also doesn't shows significant load.
So analyse of the same jacoco.exec file on idle jenkins taking 30-50 seconds, but on production jenkins it can take 30-50 minutes.