The problem returned after changing the max builds back to 500 for the job in question. We kept upping the -Xmx value and jenkins continued to run out of memory and the web ui would become unusable, with most requests timing out.
We eventually settled on -Xmx16384M and the jenkins monitoring plugin showed the junit xml processing cresting the 16GB watermark. We upgraded from v1.8 of the junit plugin, to the latest version v1.9, and experienced the same excessive memory usage. The junit.xml file has includes 51,000 tests and is about 17MB in size. Is that indicative of a job that has too many tests within it? Please advise, we have turned off junit processing on the job in question and our memory usage has dropped to below 4GB. Thank you! > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/decd1354-c50a-4848-bcd5-68f3e4cdd414%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
