On Tuesday, 13 August, 2019 03:44, test user <[email protected]> wrote:
>On this page: >https://www.sqlite.org/asyncvfs.html >Quote: The use of WAL mode largely obviates the need for this >asynchronous >I/O module. >The WAL mode does not change the fact that these operations will >still >block the application process that embeds SQLite: > > - Slow read queries. > - A large amount of writes. > >So would something like the original async module still be useful, >even with WAL mode? In WAL mode one may achieve a similar effect by simply setting the autocheckpoint to 0 pages and running the checkpoint operations in their own thread. This will prevent the checkpoints from delaying the COMMIT operation because no autocheckpoint is done at any COMMIT time ever, and move the overhead taken to do the checkpoint to another thread separate from the threads performing database operations. Not exactly the same, but probably better since it will not affect the ACID properties of the database and have no effect on sharing the database file amongst multiple processes. -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
