Uploaded image for project: 'Code Tools'
  1. Code Tools
  2. CODETOOLS-7902599

jcstress deopt rework: favor deopt-all, once per test

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • None
    • None
    • tools
    • None

      As demonstrated by CODETOOLS-7902598, getting the full classes list is expensive. Also, deopting one method after another would yield many safepoints. The only reason to favor individual deopts is to avoid deoptimizing Java compilers like Graal, where the cost of deopting the compiler itself is greater than the cost of deopting individual methods. For that, we would need to introduce an escape hatch. The probabilistic deopt serves little purpose as well: we need to be more deterministic and deopt before starting another test, not accept deopt in the middle of it.

            shade Aleksey Shipilev
            shade Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: