On Wed, Feb 27, 2013 at 3:24 AM, Rob Turpin <flax3...@gmail.com> wrote:
> I wrote up a test case to do some performance tests for the update > statement, and I'd thought I'd ask before probing around the code first. > > For SQLite3: 280,000 updates per second > For SQLite4: 290 updates per second > > So why the abysmal drop for the in memory SQLite4? > I ran this in the profiler and saw that the SQLite4 is spending 97.53% of its time (literally) in a single debugging check inside of the in-memory KV storage engine: assertUpPointer(). This routine is entirely option, of course, and is there merely to verify the integrity of the binary tree used for storage. If you disable that one routine, the in-memory database is very fast, it seems. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
