Thank you Jesse! I'll check it out. One more thing, the plugin uses the stored output files (.exec files created by JaCoCo) to examine them when showing the reports. Maybe the problem is that the plugin loads the serialized objects and the exec files too. What do you think?
Thanks, Ogi On Wed, Jan 2, 2013 at 10:06 PM, Jesse Glick <[email protected]> wrote: > On 12/27/2012 10:25 AM, Ognjen Bubalo wrote: > >> A plugin (JaCoCo) uses too much memory. I would like to investigate it, >> but first I need to understand what does the Jenkins serialize and when. >> Can someone please >> describe me which objects are saved and retrieved and when generally? I >> see that it is saved into a build.xml. >> > > Yes, various objects associated with the build, such as an Action, are > serialized via XStream. But what is serialized is not your concern if you > are investigating heap memory consumption. > > You can use org.jvnet.hudson.test.**MemoryAssert (in newer core versions) > to check heap usage of a build from a functional test (e.g. using > JenkinsRule). Recentish changes done in the Cobertura plugin illustrate how > you can use automated tests to verify that proposed changes really relieve > memory pressure. > > The Database plugin [1] is probably what you will need for a long-term > fix; see the thread on this topic. > > > [1] > https://wiki.jenkins-ci.org/**display/JENKINS/Database+**Plugin<https://wiki.jenkins-ci.org/display/JENKINS/Database+Plugin> >
