Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8228573 Analyse performance bottleneck in present Metal implementation
  3. JDK-8244193

Remove nextDrawableCount and lock RQ only during the blit operation

    XMLWordPrintable

    Details

    • Subcomponent:
      2d
    • CPU:
      generic
    • OS:
      os_x

      Description

      We are seeing many refresh issues like JDK-8239900, JDK-8236592, JDK-8239901.

      While analyzing these issues i noticed that if we dont return based on nextDrawableCount(basically allowing multiple mtlDrawable presents to happen per frame), we see that we update the MTLLayer properly.

      But this is causing performance regression as we rapidly consume nextDrawables and lock our RenderQueue during blit.

      Find appropriate solution for refresh issue without causing performance regression.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jdv Jayathirth D V
              Reporter:
              jdv Jayathirth D V
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: