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

MaxTenuringThreshold and AlwaysTenure/NeverTenure consistency

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 5.0u6
    • Fix Version/s: 9
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
      gc
    • Resolved In Build:
      b08
    • CPU:
      generic
    • OS:
      generic

      Description

      The AlwaysTenure and NeverTenure options were added in the 1.4.2
      time frame and are essentially equivalent to setting MaxTenuringThreshold=0
      and MaxTenuringThreshold=<max>. However, these flags are not consistently
      applied across all garbage collectors. The relationship seems to be
      reasonablely well implemented in Parallel Scavenge and somewhat
      implemented in ParNew in 1.6.0 and later, but AlwaysTenure and
      NeverTenure have no effect on the Serial collector.

      This has been a minor issue in general, but with the introduction of
      Biased Locking in 1.5.0_06, the setting for <max> is different on
      different releases. This introduces release dependent ambiguity
      on the proper setting of <max> for NeverTenure semantics. A stronger
      relationship between NeverTenure and MaxTenuringThreshold=<max> would
      eliminate the release dependent ambiguity. Making AlwaysTenure and
      NeverTenure apply to all garbage collectors would further improve
      the usability of these options.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tschatzl Thomas Schatzl
                Reporter:
                briand Brian Doherty (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: