"Stan Bielski" <[EMAIL PROTECTED]> wrote: > > Anyone care to take a guess what's going on here?
The problem is that you are thrashing. The working set on the database file is exceeding the amount of memory that your OS has set aside for disk cache. The best solution, if possible, is to insert records in sorted order by index. If you are inserting in batches, try inserting them all into a TEMP table first. Then do INSERT INTO maintab SELECT * FROM temptab ORDER BY indexcolumn; DELETE FROM temptab; If SQLite were smarter, it might be able to deal with this situation automatically. It is not clear at this time if making SQLite smart enough to deal with this is compatible with the goal of keeping SQLite small and nimble. We are working the problem. Do not expect a resolution in the near term. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
