More over, the memory usage reported by process explorer is subject to the vagrancies of the windows memory allocator. Generally the memory usage you see reported in tools is quite a bit higher than the actual memory usage of your application. First off windows manages memory in fixed size chunks so if you ask for X bytes of memory, windows allocates n contiguous chunks such that n*chunk_size >= x. However windows just reports ~ # of allocated chunks * chunk_size as your memory usage (if you use the right api). More over most applications simply report the total size of an application's "working set" which includes lots of pages of memory that are potentially shared across many applications.
On Wed, Aug 20, 2008 at 2:00 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > > On Aug 20, 2008, at 1:53 PM, Brown, Daniel wrote: > >> Looking in process explorer on XP after the disc database detached >> should a memory size change of 28 MB of RAM in the test application, I >> assumed this was the size of the database in memory. > > > That would be the peak memory usage by the application. It is not at > all clear to me that SQLite was using all 28 MB. What does > sqlite3_memory_highwater() tell you? > > > D. Richard Hipp > [EMAIL PROTECTED] > > > > _______________________________________________ > sqlite-users mailing list > email@example.com > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list firstname.lastname@example.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users