Simon, Thanks for the reply! I have read that documentation and everything else that google search would bring up on the site. Memory is constant. When you ask about "disposing of the result of one step before proceeding to the next", what exactly do you mean? Can't I theoretically call sqlite3_step() multiple times just to iterate rows? I happen to be binding the data in each row, but I thought that is optional.
Mike Borland -----Original Message----- From: Simon Slavin [mailto:slav...@hearsay.demon.co.uk] Sent: Friday, June 12, 2009 6:00 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] sqlite3_step performance degredation On 13 Jun 2009, at 1:52am, Mike Borland wrote: > I have a fairly complex program where I am seeing a performance > degradation of the sqlite3_step() function. Basically I'm iterating > roughly 200 rows at a time, over and over. The only work happening > during the iteration is I'm copying the record into an array. At > first, > sqlite3_step() takes less than a millisecond to run. After 0-50 > iterations, it's taking anywhere from 10-100ms. Read <http://www.sqlite.org/c3ref/step.html>, if you haven't already done so. Check your memory usage as you get the slow-down. Do you have a resource leak of some kind ? Are you, for example, correctly disposing of the result of one step before proceeding to the next ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
