Open
Bug 1912243
Opened 2 years ago
Updated 2 years ago
Investigate the cost and effect of using CrossProcessMutex in LSObject methods
Categories
(Core :: Storage: localStorage & sessionStorage, task, P5)
Core
Storage: localStorage & sessionStorage
Tracking
()
NEW
People
(Reporter: janv, Unassigned)
References
Details
Once we have some perf tests for localStorage (speedometer 4 might include them), we can investigate the cost and effect of using CrossProcessMutex to make localStorage fully synchronous across multiple content processes (for the same origin).
There are not many consumers of CrossProcessMutex, so I'm actually not 100% sure if it can be used for synchronizing content processes, that needs to be investigated as part of this bug.
| Reporter | ||
Comment 1•2 years ago
|
||
Note that we would still need to flush changes to parent process after each setItem which is something we want to avoid for performance reasons, so this bug is rather very low priority for now.
Priority: P3 → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•