[Webkit-unassigned] [Bug 29115] Allow multiple read transactions to run concurrently on the same DB thread

[bugzilla-daemon at webkit.org]

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





--- Comment #14 from Michael Nordman <michaeln at google.com>  2009-09-18 12:35:48 PDT ---
> let's talk a bit about this offline. ideally (performance-wise), i might want a
> list of sets of transactions: each write transaction would have its own set and
> all read transactions that are supposed to run concurrently would be put into
> the same set. and the list would really be a linked list (or similar) to allow
> O(1) removeFirst() operations. but that might be a bit of an overkill.

That sounds like a way to organize the data structures too, I think you'd lose
the ordering in which reads arrive when more than one piles up while waiting on
a write to complete, but not sure that really matters since they'd all get
started when the write completes.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.