SQLite Forum

Multi-threaded non-serialization
Login
Yes, I absolutely agree my first attempt should have worked. However I see this behavior even with the simplest read query ( SELECT value FROM table WHERE id=1 ). Running that exact query concurrently exhibits this behavior.

My table is indexed, could that be triggering a write in some way? Perhaps there are some other statistics that need to be turned off, such as "last row id" other usage relating to the previous query?

And yes, thank you for clarifying that it is a "wait time". I was wondering why the increase was so consistent. It looks like I can set that sleep value to be zero, but I will most likely just end up with a pattern in my second attempt.