Thanks Eric, you nailed it on the head! With this parameter I am able to configure the page usage and stop the memory growth where I want it!
-----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Eric Minbiole Sent: Monday, June 29, 2009 12:06 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Memory leak with sqlite3_exec on qnx 6.4.1 > So it seems by best bet is to close and open the connection once every 5 > minutes or so? While this might "work", I don't think you should resort to that. As Kees noted earlier, there will be performance drawbacks if you close/re-open the database. As others have indicated, the heap growth is likely due to SQLite intentionally caching frequently used disk pages in order to improve performance. Rather than closing/re-opening, I suggest that you set the page cache size to a limit that is reasonable for your application: http://www.sqlite.org/pragma.html#pragma_cache_size The default is around 2MB. You can decrease to as little as 10KB. Note that there are some other buffers used by SQLite (Scratch, Lookaside, etc). However, these are typically small compared to the page cache. Additional info here: http://www.sqlite.org/malloc.html ~Eric _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users