Re: [sqlite] why does gperftools shows sqlite3_memory_used as using the largest amount of memory

2014-10-06 Thread Clemens Ladisch
Mayank Kumar (mayankum) wrote: > will the memory used by sqlite keep on increasing, if we don't > finalize at all during the life time of the db, as we do more insert/ > delete/replace operations ? Every prepared statement needs some memory (but only a small amount). As long as you are using

Re: [sqlite] why does gperftools shows sqlite3_memory_used as using the largest amount of memory

2014-10-06 Thread Mayank Kumar (mayankum)
Thanks Clemens. Gperftool a malloc replacement, profiler and leak checker, reports that the largest amount of memory was being used by sqlite3_memory_used api which sounds weird, as it just reports the value of some counters. So it might be an error in gperftools itself. Not sure. I found

Re: [sqlite] why does gperftools shows sqlite3_memory_used as using the largest amount of memory

2014-10-03 Thread Clemens Ladisch
Mayank Kumar (mayankum) wrote: > -my application sqlite based runs for months before it might get restarted > -while its running there are places we need to execute the following series :- > - sqlite3_bind_int64(deleteStmt > - sqlite3_step(deleteStmt) > -

Re: [sqlite] why does gperftools shows sqlite3_memory_used as using the largest amount of memory

2014-10-02 Thread Mayank Kumar (mayankum)
Thanks Richard, I will use sqlite3_memory_used and get back on this thread. Gperftools was written by google(Sanjay Ghemawat) and is maintained here https://code.google.com/p/gperftools/ I will check on their support list to see if this is a known issue. I have a related question though:- -my

Re: [sqlite] why does gperftools shows sqlite3_memory_used as using the largest amount of memory

2014-10-02 Thread Richard Hipp
On Thu, Oct 2, 2014 at 2:21 PM, Mayank Kumar (mayankum) wrote: > Hi All > I am using sqlite 3.7.7.1 > > When profiling my application using gperftools-2.0, the profile always > shows sqlite3_memory_used as the top user of memory. My first guess: A bug in gperftools-2.0.