On Sat, Jan 14, 2017 at 1:09 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 14 Jan 2017, at 8:54am, Clemens Ladisch <clem...@ladisch.de> wrote: > >> If your use case is more complex than the simple mechanism offered by >> SQLITE_CONFIG_PAGECACHE, consider using SQLITE_CONFIG_PCACHE2 (or >> SQLITE_CONFIG_MALLOC). > > However, the improvement in time provided by this may not be as great as you > think. > Before investing lots of time in building special page-size-handling into > your program, > do some tests in a demo application running on your hardware. You can spend > a forty > hours learning all about the internals of SQLite just to end up with a speed > increase of 1%. > And then you have a ton of complicated low-level code to maintain.
Yes, we're not looking for speed-ups, primarily, but rather reduced heap fragmentation and control over memory usage. SQLITE_CONFIG_PCACHE2 is definitely furthest down on my list, for precisely the reasons you quote. - Kim _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
