On Wed, Jan 18, 2012 at 3:12 PM, John Elrick <john.elr...@fenestra.com>wrote:
> > Total times _malloc called in test: 69,859,114 > > Times calling _malloc: 57,679,282 > sqlite3Parser(10) > sqlite3RunParser(9) > sqlite3Prepare(8) > sqlite3_prepare(7) > sqlite3_exec_inner_loop_invoke_callback(6) > sqlite3_exec_outer_while(5) > sqlite3_exec(4) > sqlite3Parser(3) > sqlite3RunParser(2) > sqlite3Prepare(1) > sqlite3_step(0 > It looks like you might be doing something that is forcing SQLite to constantly reparse the schema. * CREATE or DROP statements * Registering new collating sequences * Registering new application-defined functions * ATTACH * VACUUM Maybe set a breakpoint on sqlite3ResetInternalSchema() to find out what is making the schema be reparsed so much. > > Times calling _malloc: 2,775,682 > sqlite3RunParser(9) > sqlite3Prepare(8) > sqlite3_prepare(7) > sqlite3_exec_inner_loop_invoke_callback(6) > sqlite3_exec_outer_while(5) > sqlite3_exec(4) > sqlite3Parser(3) > sqlite3RunParser(2) > sqlite3Prepare(1) > sqlite3_step(0) > > Times calling _malloc: 2,775,682 > sqlite3Prepare(8) > sqlite3_prepare(7) > sqlite3_exec_inner_loop_invoke_callback(6) > sqlite3_exec_outer_while(5) > sqlite3_exec(4) > sqlite3Parser(3) > sqlite3RunParser(2) > sqlite3Prepare(1) > sqlite3_step(0) > > Times calling _malloc: 2,092,350 > sqlite3Parser(3) > sqlite3RunParser(2) > sqlite3Prepare(1) > sqlite3_step(0) > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
