Dinu wrote: > The WAL size is in excess of 9G atm. > The WAL size is growing ever slower (was about 10M/s, now it's 1M every 2s, > slowing down). This indicates to me a non-linear process that I can link > only to the B-trees, it's the only non-linear component I can think of that > could cause this slowing-down-to-a-drag.
The WAL file contains the new version(s) of any modified page; for every page access, the database has to search in the WAL for the newest version. Consider using DELETE/TRUNCATE/PERSIST journal mode instead; any changed pages are copied to the journal before being modified, so there is never more than one copy of a page in the journal. And during normal operation, the database never has to look at the contents of an old page. Alternatively, try copying all the other rows to a new table, and dropping the old one. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
