[Webkit-unassigned] [Bug 104310] New: IndexedDB: put() should index asynchronously
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Dec 6 15:38:31 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=104310
Summary: IndexedDB: put() should index asynchronously
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore Misc.
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: alecflett at chromium.org
As reported on chromium-html5@ - calling put() with lots of indexes can be a serious performance drag, probably partially because the frontend put() has to resolve all the values and send a giant blob of index data to the backend - the value resolution happens synchronously, before the backend even sees it.
What we should probably be doing is sending the indexing data to the backend, and generating some kind of separate event in the frontend to generate the index data & send it to the backend using setIndexKeys()
This is kind of how createIndex() works, and it would probably have to have the same kind of semantics...
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list