Closed Bug 1494775 (picture-caching) Opened 6 years ago Closed 6 years ago

[meta] Picture caching

Categories

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

64 Branch
enhancement

Tracking

()

RESOLVED FIXED

People

(Reporter: jrmuizel, Assigned: gw)

References

Details

(Keywords: meta)

This tracks the picture caching work happening upstream.
Assignee: nobody → gwatson
Alias: picture-caching
Blocks: 1436193
Blocks: 1480945
Blocks: 1463640
Blocks: 1422567
Priority: -- → P2
Blocks: 1414575
Blocks: 1463318
See Also: → 1503794
No longer blocks: 1503794
Depends on: 1503794
Keywords: meta
Summary: Picture caching → [meta] Picture caching
Blocks: 1459187
Depends on: 1514490
Depends on: 1514491
Depends on: 1514539
Depends on: 1515540
Depends on: 1516183
Depends on: 1516695
Depends on: 1516753
Depends on: 1516786
Depends on: 1516839
Depends on: 1517117
Depends on: 1517481
I see some nice performance & power wins with picture caching enabled on Mac. e.g. scrolling arstechnica.com:- picture caching off ~45 fps; 14 ms GPU time, picture caching on ~60 fps; 9 ms GPU time. leaving the small throbber onscreen from https://bugzilla.mozilla.org/attachment.cgi?id=8962814 :- WR off, 2 W CPU + 4 W GPU, total processor package uses 9 W WR on caching off, 1.5 W CPU + 8 W GPU, total processor package 12 W WR on caching on, 1.5 W CPU + 2 W GPU , total processor package uses 5 W Nice! Thanks. (MacBookPro11,1 @1440x900, gfx.compositor.glcontext.opaque TRUE, Nightly 2018-01-03)
Depends on: 1517788
Depends on: 1517805
Depends on: 1518013
Depends on: 1518050
Depends on: 1518406
Depends on: 1518407
Depends on: 1518405
Depends on: 1518513
Depends on: 1518796
Depends on: 1519411
Depends on: 1519609
Depends on: 1520114

Now that this is landed and enabled by default, should we close the meta and track bugs individually? Or is it best to leave this open for now?

Flags: needinfo?(jmuizelaar)

Let's close it.

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jmuizelaar)
Resolution: --- → FIXED
Depends on: 1527380
You need to log in before you can comment on or make changes to this bug.