[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 #13 from Dumitru Daniliuc <dumi at chromium.org>  2009-09-18 11:54:05 PDT ---
(In reply to comment #11)
> You know, in looking at this more closely, maybe you should take a stab at
> modifying your data structures to better match the type of logic that needs to
> be applied to them. Iterating over a wanna be FIFO queue is just not quite
> right. I think you've managed to implement the desired behavior despite the
> data structures, but they're not working in your favor.
> 
> struct CoordinationInfo {
>   Q pendingTransactions;
>   Set activeReadTransactions;
>   Transaction* activeReadWriteTransaction;
> };
> 
> That may be easier to reason about.

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.

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