Hi all, great questions: *Re: Why VACUUM.* We vacuum weekly. This particular database is a "rolling journal" -- we are constantly adding new rows to the end of the table, and every week we truncate off the head of the journal to only keep 3M rows at the "tail". Given that we're truncating the "head", without vacuuming we'd be inserting the new rows at the "front" of the database with the old rows at the "end" -- and then each truncation would leave the database more and more fragmented. Granted, this is on SSDs so the fragmentation doesn't matter a *ton*, but it just adds up and gets worse over time. Anyway, agreed it's not the most important thing to do, but all things being equal I'd like to do it if I can to keep things clean and snappy.
*Re: "a simple way is to sleep in the progress callback"* -- Can you tell me more about this? Are you referring to the callback provided to sqlite3_exec(), or something else? Thanks! -david On Mon, Dec 8, 2014 at 3:16 PM, Roger Binns <rog...@rogerbinns.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/08/2014 01:35 PM, Max Vlasov wrote: > > I wonder whether I/O "sleeping" possible in the first place. > > In this particular case the OP wants to vacuum while the machine is > doing other I/O activity unrelated to the vacuum. Having more > sleeping during the vacuum will allow the other I/O a greater share. > > Roger > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iEYEARECAAYFAlSGMTgACgkQmOOfHg372QRxMACgz3qZHBGcUrOyf4DkFR5Km1a4 > jm4AoL49txXLfzPQefbjlnGg9UZ4GtcP > =9gAV > -----END PGP SIGNATURE----- > _______________________________________________ > 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
