Closed Bug 1492397 Opened 3 years ago Closed 2 years ago
Render Bridge Parent creation to async in content process
SendPWebRenderBridgeConstructor() is sync ipc, it is better if the ipc is async.
(In reply to Sotaro Ikeda [:sotaro] from comment #0) > SendPWebRenderBridgeConstructor() is sync ipc, it is better if the ipc is > async. It is possible when SendPWebRenderBridgeConstructor() is in content process.
Summary: Make SendPWebRenderBridgeConstructor() to async → Make SendPWebRenderBridgeConstructor() to async in content process
With Bug 1493327 patch, latency became better. With it, I did not see more than 4ms latency.
Summary: Make SendPWebRenderBridgeConstructor() to async in content process → Make WebRenderBridgeParent creation to async in content process
Attachment #9013930 - Attachment is obsolete: true
Sotaro does this need to block the MVP?
I do not thinks this needs to block the MVP. In the past, WebRenderBridgeParent creation took longer time(more than 10ms). But since Bug 1493327, the creation time is normally less than 1ms.
I rechecked the latency with attachment 9013195 [details] [diff] [review]. The majority of cases, the latency was less than 0.1 ms. And the longest latency was 1.5ms. Then, the latency is not a problem now.
The latency problem was addressed by Bug 1493327. Re-open it, when the latency becomes problem.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.