Den 17 feb. 2017 5:33 em skrev "Richard Hipp" <d...@sqlite.org>:
On 2/17/17, Kim Gräsman <kim.gras...@gmail.com> wrote: > > If we let it use malloc directly and control it > with the soft heap limit, we'll have a steadily rising memory curve > until all caches are fully loaded (could take weeks.) > Caches get flushed from time to time, for example when another process writes to the database. If that does not work out, you can always reclaim memory on demand using "PRAGMA shrink_memory;" (https://www.sqlite.org/pragma.html#pragma_shrink_memory) or equivalently sqlite3_db_release_memory(). Both will call free() on unused cache lines Thanks, shrink_memory could come in handy. But this is not the problem we're trying to solve -- rather we want to claim as much memory as possible up-front to make mem usage deterministic and make it easier to diagnose other subsystems with run-away memory usage. - Kim _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
