Re: [sqlite] SQLITE_ENABLE_STAT3/4 causing expensive statement recompilation

2013-12-12 Thread Dominique Devienne
On Thu, Dec 12, 2013 at 4:19 PM, Richard Hipp wrote: > On Wed, Dec 11, 2013 at 3:00 PM, Nick Hutchinson >wrote: > > > I ran my test app under Visual Studio's profiler, and saw that a > > substantial amount of time is spent in calls to

Re: [sqlite] SQLITE_ENABLE_STAT3/4 causing expensive statement recompilation

2013-12-12 Thread Richard Hipp
On Wed, Dec 11, 2013 at 3:00 PM, Nick Hutchinson wrote: > I ran my test app under Visual Studio's profiler, and saw that a > substantial amount of time is spent in calls to sqlite3Reprepare(). Reading > the docs at http://www.sqlite.org/c3ref/prepare.html, I assume

[sqlite] SQLITE_ENABLE_STAT3/4 causing expensive statement recompilation

2013-12-11 Thread Nick Hutchinson
Hi, I'm finding that if I compile with either SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4, repeatedly executing a prepared SELECT statement is substantially slower. I have a silly benchmark app that populates a database with test data, creates some pertinent indexes, runs ANALYZE, then executes a