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

Analyse performance bottleneck in present Metal implementation

XMLWordPrintable

    • 2d
    • x86_64
    • os_x

      Compared to OpenGL rendering is very slow in present Metal implementation.
      Also we see lot of flickering when we move between different UI components. This might be because of improper state management.

        1. Performance_improvement_timeline.png
          Performance_improvement_timeline.png
          179 kB
        1.
        		 Lock the RenderQueue in main thread before we start Blitting Sub-task Closed Jayathirth D V  
        2.
        		 Use setNeedsDisplay to start blitting in Appkit thread in Metal Sub-task Resolved Jayathirth D V  
        3.
        		 Use single render encoder per destination for metal Sub-task Resolved Jayathirth D V  
        4.
        		 Check how Toolkit.Sync() is affecting J2DBench numbers Sub-task Closed Jayathirth D V  
        5.
        		 Remove CALayerDelegate usage for metal Sub-task Resolved Jayathirth D V  
        6.
        		 Refactor code to remove repetative logic in MTLLayer Sub-task Resolved Jayathirth D V  
        7.
        		 Verify usage of CHECK_PREVIOUS_OP and how it affects performance Sub-task Closed Jayathirth D V  
        8.
        		 Remove RenderQueue lock while blitting content to front buffer Sub-task Closed Jayathirth D V  
        9.
        		 Use CAMetalDrawable texture as back buffer Sub-task Closed Jayathirth D V  
        10.
        		 Lock renderqueue for least amount of time by making CAMetalLayer asynchronous Sub-task Resolved Jayathirth D V  
        11.
        		 Use multi commandbuffer and draw back buffer in QueueFlusher Sub-task Resolved Jayathirth D V  
        12.
        		 Remove nextDrawableCount and lock RQ only during the blit operation Sub-task Resolved Jayathirth D V  

            jdv Jayathirth D V
            jdv Jayathirth D V
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: