Add deletion test, cursor read with writeback to same store.

Add deletion timing test.
Add a cursor-read-random-write test that writes back to the same store.
Turn on database deletion for all other perf tests [although the time's not counted for tests other than the deletion test].

BUG=137764
TEST=self


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=149659

[jsbell, 2012-08-01 23:05:26]

https://chromiumcodereview.appspot.com/10836063/diff/2001/chrome/test/data/in...
File chrome/test/data/indexeddb/perf_test.js (right):

https://chromiumcodereview.appspot.com/10836063/diff/2001/chrome/test/data/in...
chrome/test/data/indexeddb/perf_test.js:140: deleteDatabase(testName,
onDeleted);
Need to call db.close() before deleteDatabase() or you'll be waiting for GC to
kick in and collect it before the delete can proceed.

Tossing an onblocked handler on the delete request could log this. And/or add an
onversionchange handler to the database. Or both. :)

[ericu, 2012-08-01 23:39:43]

https://chromiumcodereview.appspot.com/10836063/diff/2001/chrome/test/data/in...
File chrome/test/data/indexeddb/perf_test.js (right):

https://chromiumcodereview.appspot.com/10836063/diff/2001/chrome/test/data/in...
chrome/test/data/indexeddb/perf_test.js:140: deleteDatabase(testName,
onDeleted);
On 2012/08/01 23:05:26, jsbell wrote:
> Need to call db.close() before deleteDatabase() or you'll be waiting for GC to
> kick in and collect it before the delete can proceed.
> 
> Tossing an onblocked handler on the delete request could log this. And/or add
an
> onversionchange handler to the database. Or both. :)

Added onblocked.

[ericu, 2012-08-01 23:40:17]

And fixed the close/deletion problem, and now it's all happy.

[jsbell, 2012-08-02 04:38:23]

lgtm

[commit-bot: I haz the power, 2012-08-02 17:00:01]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ericu@chromium.org/10836063/3003

[commit-bot: I haz the power, 2012-08-02 18:43:17]

Change committed as 149659