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

OopStorage concurrent iteration always requests cleanup

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • P4
    • tbd
    • 14
    • hotspot
    • None
    • gc

    Description

      End of concurrent iteration over an OopStorage unconditionally notifies the ServiceThread to do a cleanup. This is a waste of time if there's no cleanup needed, possibly needlessly spinning up the service thread. It would be better to have the case where delete_empty_blocks aborts the cleanup because of a concurrent iteration to also mark the storage as having cleanups deferred, and iteration end notify when there were deferred cleanups. That notification also ought to be taking into account the updated iteration count; if there are multiple concurrent iterations, only the last to complete should notify the service thread.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kbarrett Kim Barrett
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: