Open Bug 1533135 Opened 5 years ago Updated 2 years ago

Scrolling on bing images search results is sluggish

Categories

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

67 Branch
ARM
Android
enhancement

Tracking

()

Tracking Status
firefox67 --- affected

People

(Reporter: kats, Unassigned)

References

(Blocks 4 open bugs, )

Details

(Whiteboard: [wr-amvp][wr-q2] [sci-exclude])

I was scrolling up and down on https://www.bing.com/images/search?q=mediterranean+diet&FORM=HDRSC2 and it seemed extra sluggish.

Profile is https://perfht.ml/2SPnuay

Content process is pretty swamped, mostly building the DL and WRDL. A lot of time in memcpy. Might be some things we can improve there.

Priority: -- → P3
Whiteboard: [wr-amvp][wr-q2]
Whiteboard: [wr-amvp][wr-q2] → [wr-amvp][wr-q2] [sci-exclude]
Blocks: wr-android-perf
No longer blocks: wr-mali
Blocks: wr-mali
No longer blocks: wr-android

@jamie: Can you do a quick profile on Mali-G and T?

Flags: needinfo?(jnicol)

Profiled on Samsung Galaxy S9 (Mali-G72) and Samsung A5 2017 (Mali-T830), as well as a Pixel 2 (Adreno 540) for comparison. I think the original device was the Kindle Fire (Mali 400)

Profile shows a lot of activity during display list building, like in comment 0. Scrolling feels fine on S9 and Pixel, less so on A5. Renderer thread looks fine on Pixel and S9, but less good on A5 (albeit better than the original profile). I think it probably struggles because the main thread is so busy.

We should figure out why display list building is taking so much time. Definitely no need to block Mali-G on this, but worth tracking for Mali-T. Not because I think there's anything GPU specific, but because of the typical CPU power on those.

Mali-T profile: https://share.firefox.dev/2RKLzkD

Flags: needinfo?(jnicol)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.