Tito Ciuro <[EMAIL PROTECTED]> wrote: > Hello, > > I was reading the FAQ and I came across this statement: > > > > In practice, SQLite must read and parse the original SQL of all > > table and index declarations everytime a new database file is > > opened, so for the best performance of sqlite3_open() it is best to > > keep down the number of declared tables. > > Is there a "safe" maximum number of tables that doesn't negatively > impact too much sqlite3_open()? I wonder if it's 10, 25...? >
The more tables you have, the slower the first query will run and the more memory SQLite will use. For long-running applications where the startup time is not a significant factor, 100s or 1000s of tables is fine. For a CGI script that starts itself up anew several times per second, then you should try to keep the number of tables below a 100, I think. Less than that if you can. You should also try and keep down the number of tables in low-memory embedded applications, in order to save on memory usages. Each table takes a few hundred bytes of memory - depending on the number of columns and features. -- D. Richard Hipp <[EMAIL PROTECTED]>
