Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8104949 Poor Performance for Typical Apps
  3. JDK-8105591

Should never change bounds if transform or geometry hasn't actually changed

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: P2 P2
    • fx1.0
    • None
    • javafx
    • None

      Simple case of not guarding against duplicate settings in the setter methods in Scenario. In particular, setMode() on SGAbstractShape showed up a lot in profiling. The problem is that for the most part FX filters out duplicate settings, but in situations where FX doesn't do this, we end up invalidating the tree, repainting, accumulating dirty regions, and recomputing bounds even if the property hasn't actually changed. Simply need to guard in the setters. This alone accounted for up to 16% of the time in the bond demo.

            rbair Richard Bair (Inactive)
            rbair Richard Bair (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported: