Details

    • Type: Sub-task
    • Status: Closed
    • Priority: P4
    • Resolution: Delivered
    • Affects Version/s: 10
    • Fix Version/s: 10
    • Component/s: hotspot
    • Subcomponent:
    • Verification:
      Verified

      Description

      The default value for `BiasedLockingStartupDelay` has been changed to 0. The flag `BiasedLockingStartupDelay` previously had the default value 4000 which delayed the use of biased locking with 4 s (4000 ms). The reason for this delay was performance but recent performance runs show no difference between the 4000 ms delay and no delay. Since having the delay will cause other parts of the VM to do extra work, having the default set to 0 makes more sense.

        Attachments

          Activity

            People

            • Assignee:
              sjohanss Stefan Johansson
              Reporter:
              mlautman Mary Lautman
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: