Open Bug 1544052 Opened 5 years ago Updated 2 years ago

Consider using RKV for PersistentCache.jsm

Categories

(Firefox :: New Tab Page, enhancement, P3)

Product:
Firefox
Component:
New Tab Page
Type:
enhancement

Tracking

()

People

(Reporter: k88hudson, Unassigned)

References

Details

We're seeing that PersistentCache.jsm is potentially slowing us down at start-up, can we do some preliminary to swap RKV in and see if it would improve the read time at start up?

Type: defect → enhancement
Priority: -- → P1

Yes, that's definitely the perfect use case for rkv (kvstore in the JS world).

I think we can make the switch once the rkv memory regression gets fixed (bug 1543795).

Depends on: 1543795

Looks like we're doing both reads and writes during startup. Is there a way to defer writes for rkv or is it on the caller to request a write later?

Blocks: 1534775
Priority: P1 → P2
Blocks: pocket-newtab-69
Blocks: pocket-newtab
No longer blocks: pocket-newtab-69
No longer blocks: pocket-newtab-68
Assignee: nobody → sdowne
Priority: P2 → P1
Assignee: sdowne → nobody
Priority: P1 → P2
Component: Activity Streams: Newtab → New Tab Page
Priority: P2 → P1
Depends on: 1565035
Blocks: perf-tweaks
Priority: P1 → P3
No longer blocks: pocket-newtab
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.