That actually depends on a lot of things like what you need the database, how often you query it, what hardware it runs on and how the schema is designed. You really can't say with filesize alone.
Like honestly you should just look at your queries and how long they take to execute. If they take too long first look at your code if you actually need all those queries and check if you can optimize them by doing smarter joins, reducing the amount of queries through batching inserts or updates, etc.
After all that maybe you should look at a different database solution.
Jerome
in reply to Neil E. Hodges • • •Neil E. Hodges likes this.
SuperDicq
in reply to Neil E. Hodges • • •Neil E. Hodges likes this.
Angry Sun
in reply to SuperDicq • • •SuperDicq
in reply to Angry Sun • • •SuperDicq
in reply to SuperDicq • • •Like honestly you should just look at your queries and how long they take to execute. If they take too long first look at your code if you actually need all those queries and check if you can optimize them by doing smarter joins, reducing the amount of queries through batching inserts or updates, etc.
After all that maybe you should look at a different database solution.
Neil E. Hodges likes this.
bonifartius
in reply to Neil E. Hodges • • •Implementation Limits For SQLite
www.sqlite.orgNeil E. Hodges likes this.
balduin
in reply to Neil E. Hodges • • •