Am 30.10.2013 um 16:47 schrieb Ruben van Staveren <[email protected]>:
> Hi, > > I am a Jenkins administrator for a site with not that many jobs, but these > jobs keep a constant rate of massive compiler warnings (~9000 - 10000). > For a particular job for a software with multiple versions the per build > build.xml log file that is generated and kept by Jenkins is around ~13MB. The > analysis.xml containing the compiler warnings is around ~ 8.5 MB. With 14 > jobs each keeping 14 days of history brings the total Jenkins has to scan to > ~2.1 G. > What dashboards are visible? Most (if not all) compiler warnings graphs do not read the analysis.xml file at all. These files are only read when a user drills down to a warning. > Only be removing jobs from the dashboard view made it responsive again. I > still observed some lag switching between other views, but when I had reduced > the amount of jobs it seemed Jenkins was able to keep everything in core. The > "All" pane is still unusable due to this. > > The bulk of the build.xml seems to consist out of > ~ 89000 lines of cppcheck data > ~ 87000 lines of sloccount data > This seems to be the problem! The build.xml file should be as small as possible since these files are always read (and are always kept in memory). Seems that these plug-ins do not use an additional file to store the data: this is a bug (or at least a bad design). Can you please file a new bug report for both plug-ins? Is the performance better if you disable the cppcheck and sloccount plugins? What other warnings are you aggregating in the analysis.xml file? Are these produced by the warnings plugin? > > Trimming these sections from the build.xml leaves it only ~ 430 lines > > The analysis.xml is around ~183500 lines. > > Except for the team fixing the compiler warnings, reducing the amount of jobs > per dashboard view, shorter retention periods for build data, no graphs in > dashboards, deleting old jobs, is there any way in where Jenkins can be tuned > to handle these warning heavy jobs ? > > Best Regards, > Ruben van Staveren > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" 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/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
