Check how much heap you have allowed jenkins to use. If too low unit tests will spend a hugely disproportionate % of their time in garbage collection and loading from disk rather than parsing the results (load the prior build to get the failing since for a test, do the next test get the previous result for that test (which normally will now be in memory,but will have been garbage collected and will need loading form the disk again) rinse repeat....
On Friday, October 9, 2015 at 3:11:33 PM UTC+2, Tim wrote: > > I run jobs that have that many, one with about 80,000 tests. of course > there's a lot of work going on, but I wouldn't call it a painful slowdown. > > On Thursday, October 8, 2015 at 2:25:22 PM UTC-4, Kevin Goess wrote: >> >> Is 51,000 tests too much in a single job? >> >> We're seeing painful slowdowns in the Jenkins UI and this question came >> up. Our junit.xml file is about 17MB in size. Are other people running >> that number of tests successfully? >> >> >> >> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/908c5620-2893-4b2f-bbca-861664aef43f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
