RFR: 8319251: [REDO] Change LockingMode default from LM_LEGACY to LM_LIGHTWEIGHT

Daniel D. Daugherty dcubed at openjdk.org
Tue Mar 19 19:58:19 UTC 2024


On Tue, 20 Feb 2024 16:40:05 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:

> A fix to change LockingMode default from LM_LEGACY to LM_LIGHTWEIGHT.

Here's my stress test results rollup:

     - StressWrapper_Inflate2_8H stress results:
       - linux-x64 passed release, fastdebug, slowdebug bits for run-[1-3]
       - macosx-aarch64 passed release, fastdebug, slowdebug bits for run-[1-3]
     - StressWrapper_MoCrazy_8H stress results:
       - linux-x64 with 1024 threads timed out:
         - release bits run-1 after 429 of 480 minutes
         - release bits run-2 after 430 of 480 minutes
         - release bits run-3 after 433 of 480 minutes
         - fastdebug bits run-1 after 449 of 480 minutes
         - fastdebug bits run-2 after 446 of 480 minutes
         - fastdebug bits run-3 after 443 of 480 minutes
         - slowdebug bits run-1 after 473 of 480 minutes
         - slowdebug bits run-2 after 474 of 480 minutes
         - slowdebug bits run-3 after 473 of 480 minutes
       - macosx-aarch64 with 32 threads passed fastdebug, slowdebug bits for
         run-1; the release bits log due to a strange build error:
             /bin/bash: /System/Volumes/Data/work/shared/bug_hunt/
             8319251_for_jdk23.git/build/macosx-aarch64-normal-server-release/
             make-support/build-times/build_time_start_TOTAL_human_readable:
             No such file or directory
       - macosx-aarch64 with 32 threads passed release, fastdebug, slowdebug
         bits for run-[23]

I'm running the same stress testing on the baseline jdk-23+14-1012 bits
to see if I get the same results. In particular I want to know if
StressWrapper_MoCrazy_8H also hangs on linux-x64 with baseline bits.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/17932#issuecomment-2008003599
PR Comment: https://git.openjdk.org/jdk/pull/17932#issuecomment-2008006020


More information about the hotspot-runtime-dev mailing list