Open
Bug 1260254
Opened 8 years ago
Updated 2 years ago
Lazy load tabs on session restore
Categories
(Firefox :: Session Restore, defect)
Firefox
Session Restore
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox48 | --- | affected |
People
(Reporter: canuckistani, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf)
In bug 1257554 we removed a checkbox that allows the user to require all tabs are loaded on restart. What we should actually do on session restore is: a) immediately load the current tab b) in a sequence, load/prefetch pinned tabs c) load/prefetch other tabs
Comment 1•8 years ago
|
||
Jeff, how does this feature request differ from the existing behavior when the "browser.sessionstore.restore_on_demand" pref = false? By "lazy load tabs", do you mean restore on demand/focus or restore leisurely in the background?
Component: General → Session Restore
Flags: needinfo?(jgriffiths)
Reporter | ||
Comment 2•8 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #1) > Jeff, how does this feature request differ from the existing behavior when > the "browser.sessionstore.restore_on_demand" pref = false? By "lazy load > tabs", do you mean restore on demand/focus or restore leisurely in the > background? There are two key differences: 1. pinned tabs would not restore on start, but shortly afterwards and not all at once 2. other tabs would restore in the background An implementation detail of this idea I think is important is, at no time should we ever load more than 1 or 2 tabs, I think currently we suffer from a thundering herd problem with any number of documents attempting to load all at once. With pinned tabs this is even worse because the types of sites that get pinned are much heavier ( gmail, irccloud, fb )
Flags: needinfo?(jgriffiths)
Comment 3•8 years ago
|
||
(In reply to Jeff Griffiths (:canuckistani) (:⚡︎) from comment #2) > An implementation detail of this idea I think is important is, at no time > should we ever load more than 1 or 2 tabs, I think currently we suffer from > a thundering herd problem with any number of documents attempting to load > all at once. btw, in my investigation of bug 1037179, I saw that session restore appears to be throttled to load three tabs at a time. In contrast, "Open All in Tabs" from a bookmarks folder is not throttled and will try to load 10–20 tabs simultaneously.
Comment 4•8 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #3) > (In reply to Jeff Griffiths (:canuckistani) (:⚡︎) from comment #2) > > An implementation detail of this idea I think is important is, at no time > > should we ever load more than 1 or 2 tabs, I think currently we suffer from > > a thundering herd problem with any number of documents attempting to load > > all at once. > > btw, in my investigation of bug 1037179, I saw that session restore appears > to be throttled to load three tabs at a time. In contrast, "Open All in > Tabs" from a bookmarks folder is not throttled and will try to load 10–20 > tabs simultaneously. exactly right there should be a pref to control both behaviors (most users like to load tabs or bookmarks at once/ or 1 or 2 at a time)
Comment 5•8 years ago
|
||
would love to see tabs after session restore throttled and load 1–2 tabs simultaneously(user's pref of 1 or 100 whatever the user like)
Comment 7•8 years ago
|
||
I think it might be, yes. I suspect bug 1256472 is about taking advantage of the work going on in bug 1243707.
Updated•7 years ago
|
Blocks: ss-feature
Wasn't this handled with bug 906076?
Updated•2 years ago
|
Severity: normal → S3
Comment 9•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 25 votes.
:dao, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(dao+bmo)
Comment 10•2 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Flags: needinfo?(dao+bmo)
You need to log in
before you can comment on or make changes to this bug.
Description
•