I guess this is what happening in my application. The WAL size has grown to 1 GB...But again my concern is why each commit is taking long time. I see a big pause before commit happens.
In a multi-threaded application, sqlite may have below limitations. Is this a fair statement? - Response time to the client application would increase because only 1 thread would be able to update database. - WAL size may grow since successful checkpoint operation is dependent on if any read operation are in a open transaction? Is there any improvements or suggestions or best practices that are being followed for Multi threaded application. Thank you, -Veeresh On Thursday, 20 February 2014 4:46 PM, Richard Hipp <d...@sqlite.org> wrote: On Thu, Feb 20, 2014 at 7:41 PM, veeresh kumar <veeru...@yahoo.com> wrote: Haven't measured the time, but I have seen a pause before commit happens. As stated during my earlier discussion, my service cannot pause for more than 10 sec as it would be result in time out for the clients that are connected to this service. > >What my understanding towards the checkpoint is taking my below settings as example, WAL size would never grow beyond 1MB because check point occurs after WAL file size reaches 1 MB. Please correct me if I am wrong. > Long-running or overlapping readers can prevent the checkpoint from occurring. The checkpoint will be retried again and again, but if there is always a read transaction open on a transaction other than the most recent transaction, the the checkpoint will never have an opportunity to run to completion and reset the WAL file. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
