SQLite Performance Advice?

Since you are not creating multiple threads, then the timer are executing things in sequence… therefore only one operation is touching the database at any given instant… that should not be a problem.

Thanks @Dave S that’s what I thought, perhaps I should have used word queued instead of threading, in any event it’s good to know not to share the connection across threads.

I was just concerned because as I created new connections over and over at 150ms without closing them that is what caused my performance issues. I know SQLite isn’t designed to be a server db and I was trying to determine if I should change my entire app to use the same global (shared) connection.

Thanks so much to everyone for their input. :slight_smile: