[
https://issues.jenkins-ci.org/browse/JENKINS-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Petti resolved JENKINS-9298.
--------------------------------
Resolution: Fixed
I'm not sure when this happened, but it now appears that Jenkins is loading
changelogs in an on-demand fashion. It shouldn't be storing large amounts of
changes in memory anymore.
Please reopen if this doesn't seem to be the case.
> Perforce plugin 1.2.3 uses a lot of memory (380+MB) storing Perforce
> changelogs
> -------------------------------------------------------------------------------
>
> Key: JENKINS-9298
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9298
> Project: Jenkins
> Issue Type: Bug
> Components: core, perforce
> Environment: Linux 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008
> x86_64 x86_64 x86_64 GNU/Linux
> total used free shared buffers cached
> Mem: 49433916 48174348 1259568 0 9206276 30870132
> -/+ buffers/cache: 8097940 41335976
> Swap: 33554424 216 33554208
> Reporter: Wren Weburg
> Assignee: Rob Petti
> Attachments: p4hudsonmemory.png
>
>
> On a Hudson server with about 60 projects we are seeing Perforce plugin
> consume in excess of 300mb JVM heap just to store Perforce changelist
> information (in class com.te42.perforce.model.Changelist, some of which have
> an arraylist of 26k items which totals 7 mb, and then there are duplicates of
> these data structures for various hudson.model.FreeStyleBuild).
> Attached is a YourKit GUI capture of the 429 mb memory dump taken by our
> YourKit profiler. This seems wrong to me because our entire P4 depot has only
> 115k changes total, and none of the projects we actually build have more than
> 6000 changelists. Plus if I do a p4 change and pipe it to a file for all 115k
> changes, the file output amounts to 10mb (decription is truncated though).
> Still, all said, the screenshot shows these data structures taking up roughly
> 400 mb in the Hudson Tomcat JVM. We are going to increase our heap from
> whatever the default is, probably 512mb, to at least 1 to 1.5 gb and hope
> that helps because right now we run out of memory for the hudson tomcat JVM
> process at least once a day and we have to restart tomcat. We'll also
> increase perm gen space. Longer term we may also upgrade to the latest
> Jenkins and rev the p4 plugin to 1.2.4 from 1.2.3. But, I still think this
> memory consumption will continue and that it's rather excessive. We do enable
> "Always Force Sync" for some projects to work around a build issue, but large
> syncs consuming heavy memory should have been fixed in p4 plugin 1.2.0
> (JENKINS-2142). Thanks for any insight! I filed as a bug simply because I
> think 300+mb worth of changelist data is unnecessary to store into memory
> unless I'm not understanding its purpose.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
