> On Aug 12, 2019, at 12:34 AM, Kira Backes <kira.bac...@nrwsoft.de> wrote: > > Our code base does not use > transactions at all (we have a segmented code base protected by > mutexes for a whole section, so reads/writes do not conflict ever).
This will really hurt performance of multiple writes, since each write statement will be followed by an implicit commit, which requires some expensive disk I/O and file system flushes. You’re also losing opportunities for parallelism by using a single connection, as SQLite allows reads on one connection to run concurrently with both reads and writes on another connection. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
