Closed Bug 1517940 Opened 7 years ago Closed 5 years ago

High CPU, bad performance on "Humble Book Bundle: Python 2019 by Packt" (clipping perf)

Categories

(Core :: Graphics: WebRender, defect, P3)

defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox66 --- affected

People

(Reporter: yoasif, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: nightly-community, perf)

Came across this report on reddit - https://www.reddit.com/r/firefox/comments/abjrtr/humble_bundles_scrolling_background_imagine_makes/ Visit: https://www.humblebundle.com/books/python-packt-2019-books Browsed to this on WR Linux and it takes up 100% of a core on my i7-7700hq. Performance profile: https://perfht.ml/2C2gqkl
I see 11ms GPU times on this page.
Priority: -- → P3
A bunch of time is being spent in C_Clip. Kats do you think this could be having the same problem you're seeing on the css 3d shooter page?
Flags: needinfo?(kats)
It looks like it could be the same problem, yeah. This page also has a perspective-transformed element (the animated background thingy at the top of the page) and the C_Clip times are high only when that is in the visible part of the viewport. That matches what I was seeing in bug 1504590 and it's likely the same root problem.
Depends on: 1504590
Flags: needinfo?(kats)
Summary: High CPU, bad performance on "Humble Book Bundle: Python 2019 by Packt" → High CPU, bad performance on "Humble Book Bundle: Python 2019 by Packt" (clipping perf)

There isn't any obvious abnormality detected in a GPU capture. We fill out a full-screen surface with those tiles (non WR tiles). Then we draw a full-screen quad (transformed) with this texture. Then, on top of it, we draw a full-screen linear gradient.

(In reply to Asif Youssuff from comment #0)

Came across this report on reddit -
https://www.reddit.com/r/firefox/comments/abjrtr/
humble_bundles_scrolling_background_imagine_makes/

Visit: https://www.humblebundle.com/books/python-packt-2019-books

It seems that web page was changed and the problem does not happen.

I tried this and it didn't seem that bad to me. Is it still bad for you with picture-caching turned on?

Flags: needinfo?(jmuizelaar)
Flags: needinfo?(jmuizelaar) → needinfo?(yoasif)

Tried to look into this and had to open Bug 1521205 - ran into a regression.

Flags: needinfo?(yoasif)
See Also: → 1521205

I don't know if this will be useful, because I'm on old hardware q6600, gf8600gt, (driver340.107) on Manjaro KDE

Clean Nightly Build ID 20190120094340 with WR disabled saturates 2 out of 4 CPU cores, animation jams/jitters:

https://perfht.ml/2HmnZs5

After restart with WR on, cpu used - just above 100% of one core, but animation looks like 5 fps, plus my mouse cursor is very laggy on whole window and moves like 5 fps too.

https://perfht.ml/2RZsP2y - ~10s without touching anything and then mouse movements

For comparison Chromium 71 don't even uses full one core of cpu and animation is butter-smooth.

To eliminate such problems I use this user script which disables all transitions and animations.

Testing again with the latest build.

CPU usage is still well above 100% across a couple of processes. Visually, everything looks fine, but I can feel the CPU heat up on my lap - with just Firefox and this page open.

Profile here: https://perfht.ml/2W4SINA but I fear it is not very interesting.

While bad, I don't think this needs to block our MVP.

Blocks: stage-wr-next, wr-perf
No longer blocks: stage-wr-trains

Either the page or WebRender has changed, but this seems to run fine now.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.