On Sun, Nov 25, 2012 at 4:12 PM, Keith Chew <keith.c...@gmail.com> wrote:
> Hi > > Ok, thanks for the all the suggestions, I will find a workaround. The > reason I am asking is that I am using sqlite to perform data > synchronisation between a server and client, and after a day, the WAL file > size can grow to 3GB, quite a bit. Performance can get really bad when you let the WAL file grow that large. You should probably try to keep the WAL file size to a maximum of a few megabytes. > I will look at improving the SQL update > to reduce some of the overhead. > > I have also found that when a record is inserted 4K is added to the WAL, > and when the record is deleted, another 3K is added. This > (insertion/deletion) happens quite a lot during data synchronisation, and > it seems to be an expensive thing (7K) in terms of WAL size growth.... > > > Regards > Keith > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
