On Mon, Jan 23, 2012 at 3:48 PM, Richard Hipp <d...@sqlite.org> wrote:
> On Mon, Jan 23, 2012 at 3:12 PM, John Elrick <john.elr...@fenestra.com > >wrote: > > > Brain hurts... > > > > Richard, more information for you. I rebuilt the call stack checking > > system into pure Delphi and confirmed that yy_reduce appears to be the > > malloc culprit. I further created a pair of procedures which I can use > to > > track the yyruleno from yy_reduce as though it were a call. Below is a > > representative sample of the data.... > > > > The parser does lots of little mallocs as it builds a parse tree. So I > expect it to generate a lot of malloc traffic. The question is why the > parser is being called so much. > > Can you put a printf() or something at > http://www.sqlite.org/src/artifact/1e86210d3976?ln=397 and figure out what > is being parsed so excessively? > > I think I can inject something to do some measurements. I seem to recall, however, that there was no substantive difference in the number of times sqlite3RunParser was called between the two. I'll check for: which query is being parsed how many times that particular query is parsed how many mallocs are stemming from that particular query. Maybe that will tell us something. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
