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

Redesign property listeners for shared classes

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P3
    • 9
    • 8
    • core-libs
    • None
    • b04
    • generic
    • generic

    Backports

      Description

        There are two approaches of making property listeners (used to invalidate callsites for inherited properties) work with shared classes. One is to remove them alltogether, replacing switchpoints with deep property guard that check the maps of all involved prototypes on each invocation, and the other is to move listeners from the ScriptObjects belonging to just one global to the property maps that are potentially shared between globals.

        At the same time there are areas where the current listener system can be optimized. Currently much more property listeners are created/registered than necessary (over 200.000 in one invocation of the Octane run.js script). Another detail that is currently less then optimal and won't work in a multi-global world is property map prototype history. We currently look up prototype history over 20 million times in one Octane run.js even though we know the object was never used with the original prototype and map.

        Attachments

          Issue Links

            Activity

              People

                hannesw Hannes Wallnoefer
                hannesw Hannes Wallnoefer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: