Closed Bug 1549471 Opened 7 months ago Closed Last month

Optimize DS cache loads and saves

Categories

(Firefox :: New Tab Page, defect, P2)

defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: thecount, Assigned: thecount)

References

(Blocks 2 open bugs)

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.

Blocks: 1534775
Assignee: nobody → sdowne
Iteration: --- → 69.1 - May 13 - 26
Priority: -- → P1
Blocks: pocket-newtab-69
No longer blocks: 1534775, pocket-newtab-68
Iteration: 69.1 - May 13 - 26 → 69.3 - Jun 10 - 23
No longer blocks: pocket-newtab-69
Blocks: perf-tweaks
Iteration: 69.3 - Jun 10 - 23 → ---
Priority: P1 → P2
Component: Activity Streams: Newtab → New Tab Page
Status: NEW → RESOLVED
Closed: Last month
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.