Issue 693260 link

Starred by 3 users

Issue metadata

Status:	Available
Owner:	----
Cc:	skyos...@chromium.org c...@chromium.org dmu...@chromium.org
Components:	Blink>Storage>IndexedDB
EstimatedDays:	----
NextAction:	----
OS:	Linux
Pri:	3
Type:	Feature

Participants' hotlists:
dmurph-future-tasks

Show other hotlists

Other hotlists containing this issue:
IDB-Performance

Investigate IndexedDB performance improvements through task scheduling

Project Member Reported by dmu...@chromium.org, Feb 16 2017

Issue description

Refine the limits for started transactions

and/or

create hard limit on queued transaction

and/or

create a scheduler for the IDB tasks

Comment 1 by jsb...@chromium.org, Feb 22 2017

Cc: skyos...@chromium.org

FYI, skyostil@ is working on a proof of concept for "activity traits" which would give insight into resource (CPU, memory, etc) across Chrome.

It seems feasible to use that to balance work across origins/connections in IDB. (For a given connection, tx ordering must be maintained, but across connections we can select arbitrarily.)