I'll send it in a bit. I actually created the complete script a week ago. Richard, I greatly appreciate your time and the attention you've given this matter. I have no doubt this is a very esoteric issue which we just happened to hit the exact combination of events to force its manifestation. As frustrating as it has been to narrow down the cause, I have nothing but respect and gratitude for everyone who has attempted to help. Thank you all. On Jan 20, 2012 3:47 PM, "Richard Hipp" <[email protected]> wrote:
> On Fri, Jan 20, 2012 at 3:40 PM, John Elrick <[email protected] > >wrote: > > > I don't mean to blow anyone off, but there are over 100 prepared queries > > involved in a very interlaced manner. Getting the EXPLAIN data is very > > time consuming and since we've gone way past that point already by > > obtaining call stack information, I am not interested in revisiting the > > territory unless there is a very good reason for it. At least I know we > > can successfully upgrade to 3.7.5 without any performance issues. It > would > > be nice to understand what is going on from that version forward, > however, > > because it is important that we be able to continue upgrades in the > future. > > > > We'd like to understand what SQLite is doing differently to cause your > problem, too. As you have already observed, most applications don't have > this issue. I'm not sure what your application is doing to make SQLite go > crazy will mallocs, but we'd like to know so that we can avoid such > situations in the future. > > Can you try this: Can you use the sqlite3_trace() interface to create a > log of all SQL statements that are evaluated. Then send me (perhaps > privately) the starting database and your log, so that I can run SQLite > through exactly the same set of operations you are running it through? > > > > > > > > > > On Fri, Jan 20, 2012 at 2:55 PM, John Elrick <[email protected] > > >wrote: > > > > > The problem is not in the queries. The problem is in a two order of > > > magnitude increase in _mallocs between the versions. The _mallocs are > > > coming from sqlite3Parser. > > > > > > > > > On Fri, Jan 20, 2012 at 2:37 PM, Max Vlasov <[email protected]> > > wrote: > > > > > >> On Fri, Jan 20, 2012 at 10:05 PM, John Elrick < > [email protected] > > >> >wrote: > > >> > > >> > The change which results in a slow down occurred between 3.7.5.0 and > > >> > 3.7.6.0. > > >> > > > >> > > > >> What about EXPLAIN difference? Or just outputs of this prefix from > both > > >> versions? > > >> > > >> Max > > >> _______________________________________________ > > >> sqlite-users mailing list > > >> [email protected] > > >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > >> > > > > > > > > > > > > -- > > > John Elrick > > > Fenestra Technologies > > > 540-868-1377 > > > > > > > > > > > > -- > > John Elrick > > Fenestra Technologies > > 540-868-1377 > > _______________________________________________ > > sqlite-users mailing list > > [email protected] > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > > > > -- > D. Richard Hipp > [email protected] > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
