<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - IndexedDB 2.0: The client's transaction operation queue should always flush to the server"
href="https://bugs.webkit.org/show_bug.cgi?id=164932">164932</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>IndexedDB 2.0: The client's transaction operation queue should always flush to the server
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>WebCore Misc.
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>beidson@apple.com
</td>
</tr></table>
<p>
<div>
<pre>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*</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>