Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8143878

Memory serialization page can become a bottleneck

    Details

    • Type: Enhancement
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 9
    • Fix Version/s: 10
    • Component/s: hotspot
    • Labels:

      Description

      When threads transition state to/from native code they use the memory_serialization_page as a means of performing memory synchronization. Due to the use of a single 4K page, and the requirement for 128byte alignment this is limited to 32 distinct slots. Combined with a poor hashing function we can get excessive contention on these slots and encounter a performance bottleneck.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              dholmes David Holmes
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: