[Webkit-unassigned] [Bug 164932] New: IndexedDB 2.0: The client's transaction operation queue should always flush to the server

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=164932

            Bug ID: 164932
           Summary: IndexedDB 2.0: The client's transaction operation
                    queue should always flush to the server
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: beidson at apple.com

IndexedDB 2.0: The client's transaction operation queue should always flush to the server

Right now, if the web page does 1000 insert's in rapid succession, the client builds up 1000 operations in the transaction queue.

We send the first insert over to the server, then wait for the response.

Then we send the second insert over.

etc etc.

Turns out - unsurprisingly - this leads to massive amounts of idle time on both the client and server side while each waits for feedback from the other.

Flushing the transaction operation queue can speed up certain usage patterns *significantly*

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161118/17fa8fe8/attachment.html>