Shared cache instance is created on file-by-file basis, i.e. if you open connections to file1.db and file2.db they will have different cache instances and any manipulations with these database files won't influence one another at all (any write operations can be executed in parallel). But if you open several connections to the same database file (from the same process of course) they all will use the same instance of shared cache (hence the word 'shared'). In this case all write operations will be "serialized" but only on table-by-table basis, i.e. if one connection is doing some updates in one table and another connection is doing updates in another table they will be able to be executed in parallel. But if different connections try to update the same table(s) they will be "serialized". So for the purpose of parallelizing transactions working with different tables you don't have to split them into different databases - with shared cache they will be parallelized pretty effectively in the same file too
Pavel. On Wed, Nov 18, 2009 at 8:19 AM, presta <harc...@gmail.com> wrote: > > To be more precise I would like to parallelize writes operations on different > tables, so potentially in different db (files). > > It's why I think about using multi databases (1 by table), the shared cache > system and the asynchronized I/O.. > > So if a shared cache is shared accross different databases, writes operation > will be "serialized", so according to all reply it seems that a shared cache > is create for each different db instance ?? > > > > > > > > > -- > View this message in context: > http://old.nabble.com/Asynchronous-I-O-and-shared-cache-tp26402983p26407565.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
