The overhead here seems like we have some unfortunate interactions between WebGL and Canvas2D. We are reading back from WebGL into the content process, and then sending that back to Canvas2D in the GPU/parent process via remoting. Seemingly vice versa as well - readback from Canvas2D to content process to send back to WebGL. Most of the churn here is in all this copying back and forth. We could do better here at least by removing the process ping-ponging, even if we still have to do some expensive copy between different WebGL contexts or D3D devices.
Bug 1908286 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The overhead here seems like we have some unfortunate interactions between WebGL and Canvas2D. We are reading back from WebGL into the content process, and then sending that back to Canvas2D in the GPU/parent process via remoting. Seemingly vice versa as well - readback from Canvas2D to content process to send back to WebGL. Most of the churn here is in all this copying back and forth, mostly towards the direction of WebGL. We could do better here at least by removing the process ping-ponging, even if we still have to do some expensive copy between different WebGL contexts or D3D devices.