Peter De Rijk wrote:
I have run into a serious performance problem with tables with many rows.
The problem only occurs on tables with an index
The time needed for an insert into a table with an index is dependend on the
number of rows. I have not formally checked, but from my tests it looks like
an exponential dependence. This of course means that while sqlite is very
fast on smaller datasets, it is slow on larger data sets and becomes unusable
on large datasets (million of rows). The insert behaviour is normal on non
indexed tables, but obviously queries are a problem then.
Is this index behaviour normal/expected for sqlite, or can this be solved?
Peter,
unless I am mistaken, inserting into a table that has an index requires
the index
to be rebuilt for each insert. Are you inserting multiple rows in a
single transaction
or not? If you could put them in a single transaction, I think the
performance
will remain adequate, even for very large tables.
Regards,
Arjen
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
