On Oct 26, 2009, at 5:00 PM, Peter Kasting wrote: > Close to two years ago, Shawn Wilsher from Mozilla asked about freeing > memory used by sqlite ( > http://www.mail-archive.com/sqlite-users@sqlite.org/ > msg30585.html ). At the > time, some benchmarks showed that setting > -DSQLITE_ENABLE_MEMORY_MANAGEMENT=1 caused a small performance hit. > > I'm looking into the same issue, this time for Google Chrome, and as > far as > I can tell the current code shouldn't cause any performance hit by > enabling > this flag. There's no additional monitoring/tracking it causes; it > just > exposes a few functions to free memory. Has the memory management > implementation changed since the previous thread, or is this feature > now > broken?
We run the "fulltest" test suite on a build of SQLite that include SQLITE_ENABLE_MEMORY_MANAGEMENT prior to every release. The sqlite3_release_memory() interface works as documented, as far as we know. Are you seeing something that would suggest otherwise? > > Also, I notice that in malloc.c, inside the #if for the above define, > there's an #if 0 protecting a call into the VDBE code. Is this > because that > code doesn't work correctly, or was it not helpful, or have the > reasons for > the #if 0 disappeared? It's not obvious to me what the code it > protects > does, so I'm not sure how much interest in it I should have. > > Thanks, > PK > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
