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

SimpleThresholdPolicy misses CounterDecay timestamp initialization

    XMLWordPrintable

Details

    • b08

    Backports

      Description

        Invocation counters always decay at the first safepoint regardless of CounterDecayMinIntervalLength when using SimpleThresholdPolicy (-XX:-TieredCompilation).
        This leads to warmup issues (e.g. observed in compiler/c2/Test8004741.java). Some methods don't get compiled as early as expected after the first safepoint.

        Reason:
        SimpleThresholdPolicy uses a dedicated class CounterDecay which contains a static timestamp. The timestamp is initialized to 0 and is_decay_needed() compares it to the current time.

        Attachments

          Issue Links

            Activity

              People

                mdoerr Martin Doerr
                mdoerr Martin Doerr
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: