x wrote: > I’ve written the console app below to illustrate. It prints out the amount of > RAM available every 20 million steps.
> GlobalMemoryStatusEx(&status); > return status.ullAvailPhys / (1024 * 1024); This is "physical memory currently available", which is affected by other things, such as the Windows file cache. Try ullAvailVirtual to see the how much your own process could allocate; this is affected by both your code and by the SQLite library. (This value is unlikely to change by much because SQLite's default cache size is 2 MB.) > It seems to lose RAM while step ascending and then give it back when step > descending. RAM that Windows chooses to use for the file cache is not lost. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
