I have a table with one TEXT column. I insert 1 million rows of short
strings, and then create an UNIQUE INDEX. The speed is very acceptable. Then
I insert another 10.000 short strings, and the performance is very bad, it
almosts take longer than inserting the initial million(!) rows to fill the
table.

Is this by design, or what can be causing this? I also observed that
inserting the additional 10.000 rows goes progressively faster when nearing
the end, I suppose because this is because at that time the index is
completely in cache. But what is the reason for the bad performance of these
 inserts? I read things about b-tree page splitting, could it be related?
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to