Update: we are also using WAL; I have noticed during a huge delete, the
WAL also grows huge. Could this also be a reason for slowness, that
SQLite duplicates every block that hosts a delete? Is there any way to
work around this?
On 17.12.2017 22:53, Dinu Marina wrote:
Hi all,
It became apparent to me from performance measurements that the DELETE
operation is very slow, when operating on large recordsets with
indexes involved. My deduction is that SQLite updates the indexes for
every deleted row, which in painstakingly slow...
Since the DELETE should be atomic, the index update could also be
atomic, and a mass pruning of the index tree is hugely faster than
individual removals.
My question is: is my deduction correct? Is there any way to
fix/improve this in userland? Or are there prospects for this to be
improved in SQLite in the foreseeable future?
Thanks,
Dinu
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
