[Webkit-unassigned] [Bug 90695] New: Performance: 2D Canvas rendering spending a lot of CPU time in RenderLayerCompositor::updateLayerCompositingState

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=90695

           Summary: Performance: 2D Canvas rendering spending a lot of CPU
                    time in
                    RenderLayerCompositor::updateLayerCompositingState
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: ASSIGNED
          Severity: Normal
          Priority: P2
         Component: Canvas
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: junov at chromium.org
                CC: simon.fraser at apple.com, senorblanco at chromium.org,
                    jamesr at chromium.org, vangelis at chromium.org


While profiling Chrome, executing the benchmark page found here:
https://github.com/sibblingz/PerfMarks

A hot spot was detected detected in RenderLayerCompositor::updateLayerCompositingState (mostly in updateGraphicsLayerConfiguration()), which appears to be called once for every 2D canvas primitive draw.
For some of the sub tests of this benchmark, as much as 20% of CPU time can be spent in that function.  Since canvas draws do not impact the layout of composited layers, there should be no need to visit this code so often.

Related bug: https://bugs.webkit.org/show_bug.cgi?id=90630

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.