Get stats on how often an IndexedDB database is used by multiple processes |
||||||
Issue descriptionPer IndexedDB related discussion in https://docs.google.com/document/d/17Xi6a5vdv_SiyptUI9PHFknt5at6131g-S2ugNhlK_g/edit#heading=h.qf9i7c52uy3r, one interesting design is to have the leveldb service hosted in the renderer for indexeddb. If another renderer process connects to the same indexeddb, then it can talk to the first renderer (like how we do it for shared/service workers). It would be insightful to gather stats on how often an indexeddb database is used by multiple renderer processes.
,
Apr 8 2016
,
May 13 2016
,
May 15 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 8 2017
Setting Internals>Services>Storage to all children of issue 611900
,
Jan 7
The Storage team monitors Internals>Storage. The Internals>Services>Storage label will be deprecated & removed. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jsb...@chromium.org
, Apr 8 2016Summary: Get stats on how often an IndexedDB database is used by multiple processes (was: Get stats on how often an IndexedDB database is used by multiple sites)