Open
Bug 1870128
Opened 2 years ago
Updated 2 years ago
Improve performance of TextureClient/Host based data with Canvas 2D recordings
Categories
(Core :: Graphics: Canvas2D, enhancement, P3)
Core
Graphics: Canvas2D
Tracking
()
ASSIGNED
People
(Reporter: aosmond, Assigned: aosmond)
References
(Blocks 1 open bug)
Details
No description provided.
Assignee | ||
Updated•2 years ago
|
Blocks: accelerated-canvas-recording
Assignee | ||
Updated•2 years ago
|
Type: defect → enhancement
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
To provide more information, we currently:
- Copy/readback the texture from the RDD to the content process
- Copy that from the content to the compositor process
And if it is a D2D or accelerated canvas, we may reupload the texture back to the GPU.
All of this when the texture is already accessible in the compositor process when we replay the recording without any copying or readbacks. There is a lot of low hanging fruit to improve performance.
You need to log in
before you can comment on or make changes to this bug.
Description
•