Large operations in sync databases

Ben Bucksch ben.bucksch at beonex.com
Tue Jul 13 20:03:07 UTC 2010


  On 13.07.2010 16:31, Andrew Sutherland wrote:
> The greater context is that rkent is implementing a new account type 
> targeted at Thunderbird 3.1.  The need for anything to be synchronous 
> is an outgrowth of the semantics of most Thunderbird message database 
> operations executing synchronously on the main thread.

I see. That is a good reason to use sync. Thanks for the explanation.

> but the best-case situation finds locks operating on a table level of 
> granularity

So instead of 2 databases, you could use separate tables and make sure 
that the long-running ops do not touch the "fast" tables, but that 
doesn't give too much advantage over 2 databases, either.

> Obviously, in the long run we want all Thunderbird activity (both core 
> and extension-provided account types) to have all their I/O happen off 
> the main thread and without storing everything in memory.

Seconded.



More information about the tb-planning mailing list