At 13:10 29/10/2008, you wrote: >Look up the implications of Sqlite's ACID feature and the use of >transactions. COMMITs are tied to disk rotation speed. On our Sqlite >databases where we look for performance we use 15,000 rpm disks and are >diligent in wrapping INSERTs, UPDATEs and DELETEs in transactions and >get very good results. > >The Sqlite B-Tree indices do slow down on insertion as extra levels are >created in the index as it grows large. That is an inherent feature of >such structures. >JS
I think the problem is that he creates the index before insert the data. He should insert the data using begin..commit and after insert creates the indexes. If not, for each insert, the indexes must be reworked/redone and slowdown happens HTH _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
