On 2 September 2017 at 22:19, Simon Slavin <[email protected]> wrote: > > And please note that you never /need/ to do any kind of VACUUM in a > production setting. The only situation where it helps is if your database > is significantly shrinking and will not grow again soon, and that’s quite > rare for a database. Doing a pointless VACUUM just means you’re wearing > out your storage device.
Good point about superflous VACUUMs, but the situation you mentioned is not the only one it helps with. VACUUM also has the side effect of rewriting the tables/indices in row order on disk, and I've observed this "defragmentation" improving performance significantly when databases are stored on network file systems (NFS3/NFS4 to be specific). I haven't seen it make a significant difference on local disk, so not really revelant to android. -Rowan _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
