RFR(T/XS) 8166275: vm/mlvm/meth/stress/compiler/deoptimize keeps timeouting

Ekaterina Pavlova ekaterina.pavlova at oracle.com
Wed Oct 23 19:13:08 UTC 2019


Hi,

The number of threads the test is launching by default is equal to (see vm/mlvm/share/MultiThreadedTest.java)
  threadsPerCpu * Runtime.getRuntime().availableProcessors() + threadsExtra

This is too much stress in case the build is debug one. For example on linux with 24 cores the test takes less
than half of minute in case of product build and more than 20 mins in case of fastdebug build.
The fix is quite trivial. It splits the test in two tests - one for product configuration and one for debug one.
The number of threads per cpu/core is reduced from 4 to 2 in case of debug build.


      JBS: https://bugs.openjdk.java.net/browse/JDK-8166275
   webrev: http://cr.openjdk.java.net/~epavlova//8166275/webrev.00/index.html
  testing: run the test on all platforms with debug and product bits


thanks,
-katya


More information about the hotspot-compiler-dev mailing list