Open
Bug 1414505
Opened 7 years ago
Updated 2 years ago
consider to evict bfcache in background tabs sooner than in foreground
Categories
(Core :: DOM: Navigation, enhancement, P2)
Core
DOM: Navigation
Tracking
()
NEW
People
(Reporter: smaug, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [MemShrink:P2])
In order to possibly reduce memory usage, but also to make foreground tab behave better (more pages there in bfcache), perhaps we should evict bfcache in background tabs sooner.
Comment 1•7 years ago
|
||
Do we have any measurements about how much memory bfcache pages take?
Reporter | ||
Comment 2•7 years ago
|
||
Well, whatever web pages happen to take. I assume it varies a lot. But no, we don't have anything. I don't think we have any measurements on web pages either, if you're talking about telemetry probes or so.
Updated•7 years ago
|
Priority: -- → P2
Comment 3•7 years ago
|
||
(In reply to Ben Kelly [:bkelly] from comment #1) > Do we have any measurements about how much memory bfcache pages take? We saw a 219MiB regression in our tabs opened measurement in AWSY when we turned this back on. It's pretty bad. See bug 1415125 and bug 1411393.
Whiteboard: [MemShrink]
Comment 4•7 years ago
|
||
This would be nice to tweak, but we think some telemetry would help us decide what to do. At this point we're not even sure how deep the cache is and how often it's used.
Depends on: 1352911
Whiteboard: [MemShrink] → [MemShrink:P2]
Updated•7 years ago
|
Blocks: MemoryOverhead
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•