I didn't read the replies, sorry if this is a duplicate.

One rare reason I saw for slowness was an index (unique) working in a transaction. Index was already corrupted but running seriously slow without any errors. Since then, whenever I encounter slowness and\or unexpected issues, I drop and recreate indexes first.

(normally 97 records would be added sub second)

Probably a radical fix (hard I know) would be to move the data to a good database like postgreSQL (even in that case, I wrote a routine to do some operations fast from a local Sqlite cache - but anyway at least much better than using native tables).


>Hi friends:
>
>A few month ago I started to have problems with my program when add records to tables.
>
>This happens at the end of the day when my system sends to server daily activity. There are up to 2 terminals and servers with W7 and W10 so I can't deduce is the OS.
>
>For example 97 records are added in 22 minutes a day when yesterday took seconds and tomorrow will take seconds again.
>
>Since there are 3 or 5 terminals is curious everyone take almost the same time when they do the process at the same time.
>
>I tried eliminate FLUSH but nothing changed.
>
>This doesn't happen in all, just a few clients. For the time it takes I think the problem is when try to lock record.
>
>Well. My clients solve the problem leaving machines turned on all night and as I started control the time I find sometimes all the process in take till 2 hours..
>
>Any ideas?
>
>Thank you.