Techno Magos wrote: > So, memory sqlite is not really usable with multiple threads (readers). > While one might expect that multiple readers of *memory *content could > scale even better than with file content.
Concurrent accesses to the same in-memory data structures must be serialized. In shared-cache mode, the connections share the cache, while on-disk connections each have their own cache. > Is there some special mode possible to achieve scaling up throughput with > multiple threads for memory sqlite content? Put a DB file on a RAM disk. Or on a normal disk (with looser synchronous and journal_mode settings), and rely on the OS file cache. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
