Closed Bug 1408421 Opened 4 years ago Closed 4 years ago
Backend thread does not overlap cpu time with the Render thread
You can see it in this profile of gmail: https://perfht.ml/2kNsK2u
It looks like this was introduced by 1365196
Bug 1365196 was added to prevent us from over producing frames. Perhaps the right solution is to only allow one extra frame.
4 years ago
If I changed the maxPendingFrameCount to 2, the scrolling looks better on windows. http://searchfox.org/mozilla-central/source/gfx/layers/wr/WebRenderBridgeParent.cpp#1144
Actually Bug 1382132 changed the maxPendingFrameCount from 2 to 1. For APZ with WR, it costs time for build_scene because of bug 1408174. I believe we can get benefit from rendering pipeline if we change the maxPendingFrameCount as 2 for scrolling. Sotaro, any thoughts?
Assignee: nobody → sotaro.ikeda.g
When maxPendingFrameCount was set to 2, there was cases that frame latency became too big. One example was that render thread always had 2 pending rendering frames. It could happen when rendering take very long. Another example was that background thread thread always had 2 pending frames. It could happen when background thread was too busy. To avoid these situation, I set maxPendingFrameCount to 1. But it restricts too much. We need to improve the performance by minimizing the latency. Just changing maxPendingFrameCount to 2 could not achieve it.
Attachment #8924492 - Flags: review?(jmuizelaar)
Comment on attachment 8924492 [details] [diff] [review] patch - Improving throttling GenerateFrame() Review of attachment 8924492 [details] [diff] [review]: ----------------------------------------------------------------- ::: gfx/webrender_bindings/RenderThread.cpp @@ +265,5 @@ > return renderer->Resume(); > } > > +bool > +RenderThread::TooMuchPendingFrames(wr::WindowId aWindowId) TooManyPendingFrames()
Attachment #8924492 - Flags: review?(jmuizelaar) → review+
Apply the comment.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/14a5ae97c682 Improving throttling GenerateFrame() r=jrmuizel
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
You need to log in before you can comment on or make changes to this bug.