Community
Participate
Working Groups
Since a while too many JDT/Core perf tests are yellow in releng perf results HTML page. Although there's a problem with the method used to decide a test must be yellow or not (Student's t-test), we must try to tune our tests to make them as green as possible...
Looking closely at measures done within each test, it seems that for some of them, warm-up is not enough. So, the JIT continues to optimize code during the measure and make them too dispersed...
Created attachment 64398 [details] Proposed patch for perf_32x branch This patch increase the warm-up for all search, build and model tests as most of them are yellow. Note that global time to run tests will not be increased as I fixed a problem on project indexing test which made 100 measures instead of 10! Also improve local perf tests storage and display to have a precise idea of what's wrong on measures when a test becomes yellow...
When bug 184015 will be fixed, we should only have approx.7 yellow tests for whole JDT/Core perfs tests on all boxes...
Fix for bug 185580 was released yesterday => consider this one as fixed for 3.3 RC1
We still have 12 tests as yellow and 2 red. Not sure this should be considered as verified for RC1.
In 3.3 M6 we had 55 yellow tests and 5 red ones. The goal was not to remove all yellow tests but try to understand why we had so many. I think we reach this goal as we have now less than 5% of yellow tests instead of more than 20%. I'll still try to reduce this number - and this would be feasible as most of the error are less than 4% (current threshold is at 3%) - but I definitely consider this bug as verified for 3.3 RC1.
I've opened bug 188043 for the too big standard error on FullSourceWorkspaceModelTests#testCloseProjects() test...