-
Bug
-
Resolution: Unresolved
-
Major
When there are a lot of test cases in a single suite, rendering the summary page is dreadfully slow. Most of the time is taken in TestObject.uniquifyName, which can be called thousands of times, each taking several msec.
[JENKINS-15818] Display exceedingly slow for large test results
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Comment |
[ We have a parameterized test with 120000 items. If one clicks on a detail then the userinterface of jenkins grinds to a halt. The fix that introduced TestObject.uniquifyName has still serious performance implications. I think what is fixed here is the summary page but clicking on a a failed test and going to the details will take forever. (I my case I waited 10 minutes and than gave up) What is fixed in this bug (remember the uniqueName) has decreased the impact of uniquifyName but I think that uniquifyName should be redesigned. ] |
Comment |
[ The {{TestObject.uniquifyName}} still has major performance issues. The AppTest.java doesn't test the original problem (test with the same name) and therefore you might think that this issue is solved. I slightly changed the AppTest.java in order to see the problem. (I will attach the new AppTest.java to this bug) The problem with the AppTest.java is that all testnames are different and this results in a bit of a fastpath in uniquifyName. How To Reproduce: - Test the new AppTest.java - Go the summary page of the build. - A number of tests will be failed now. - Click on a failed test (not the first one!) to see the detail. The last click will result in 100%cpu for a very long time. ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Other bottlenecks: CaseResult.getPreviousResult; and getSafeName called from other threads (context menu).