Re: [sqlite] Time taken to perform checkpoint operation and does it lock database during this operation?

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

Re: [sqlite] Time taken to perform checkpoint operation and does it lock database during this operation?

On 21 Feb 2014, at 12:45am, Richard Hipp wrote: > 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 >

Re: [sqlite] Time taken to perform checkpoint operation and does it lock database during this operation?

On Thu, Feb 20, 2014 at 7:41 PM, veeresh kumar 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 >

Re: [sqlite] Time taken to perform checkpoint operation and does it lock database during this operation?

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

Re: [sqlite] Time taken to perform checkpoint operation and does it lock database during this operation?

On Thu, Feb 20, 2014 at 7:08 PM, veeresh kumar wrote: > Hi, > I am using "PRAGMA > journal_mode=WAL;" with "PRAGMA synchronous=NORMAL;",with > default auto check point and page size = 1024 bytes. Since checkpoint > occurs automatically after every 1 MB, how much time it