-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: impellerImpeller rendering backend issues and features requestsImpeller rendering backend issues and features requestsengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.team-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team
Description
During some cursory profiling of impeller web, I notice that we call glCheckFramebufferStatus multiple times per frame. At least on WebGL, this is extremely slow, to the point where those calls alone are taking up 30+ms per frame (whereas the other rendering is only taking roughly 6 ms). According to MDN, glCheckFramebufferStatus can result in a full flush + round trip to the GPU.
We should consider only doing glCheckFramebufferStatus in debug builds, and simply assuming the framebuffer is complete in release builds.
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: impellerImpeller rendering backend issues and features requestsImpeller rendering backend issues and features requestsengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.team-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team