Closed
Bug 1549471
Opened 5 years ago
Closed 5 years ago
Optimize DS cache loads and saves
Categories
(Firefox :: New Tab Page, defect, P2)
Firefox
New Tab Page
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: thecount, Assigned: thecount)
References
Details
Attachments
(1 file)
Right now DS saves everything in one big cache.
Next time we go to load it, the first thing we try to load is for reportCacheAge, which tries to load all the cache, just to get a small piece of it.
The next time we go to load cache, it's fast because it's all been put into memory. This makes our cache load very front heavy. We could split it up, and possibly get some noticeable startup gains. Make these files in the profile, in a directory, instead of 1 file for everything.
I suggest we break our cache up into logical blocks, cache ages in one block, spocs in another, layout in another, and feeds in another. I considered putting feeds into a cache file for each feed, but not sure, feels like overkill.
|
||
Updated•5 years ago
|
Assignee: nobody → sdowne
Iteration: --- → 69.1 - May 13 - 26
Priority: -- → P1
|
Assignee | |
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
|
||
Updated•5 years ago
|
Blocks: pocket-newtab
|
|
Assignee | |
Updated•5 years ago
|
Iteration: 69.1 - May 13 - 26 → 69.3 - Jun 10 - 23
|
|
||
Updated•5 years ago
|
No longer blocks: pocket-newtab-69
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
|
|
||
Updated•5 years ago
|
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.
Description
•