Sqlite limitations for freehosting

I would like to create small dating site running on your freehosting. It will have a lot of criteria to compare the properties between users. So I want to ask two questions on sqlite for general because I would like to write effective php app, that will not be hard for CPU or db performance. First of all - what is ideal count of columns for a single table on your server. May be like 50 columns OK? Or is it too much and should I normalize and add more tables then?
There will be lots of columns for user table like: id, sex, age, height, bmi, dress size, body measures (4 columns), hair color, hair length, community, sport, hobbies, region (a number) town (number), faith, children, category.
My question is if can I create more sqlite dbs or files and where is the limit. I would like to make the db smaller separated files. So when the user will look for users with certain criteria, the db of the needed criteria would be connected. I believe this should make the search faster. So I can imaging I can separate the sqlite data to 15 or 30 smaller files. Is this possible?

If you are concerned about the size of the database and performance causing trouble, I would suggest skipping SQLite entirely and use MySQL instead. MySQL is more capable of handling large databases efficiently, and also can deal a lot better with more concurrent activity. And we run MySQL on separate servers configured specifically to run MySQL well, which we can’t do for an SQLite database in your hosting account.

Because SQLite databases are just files on your hosting account, the usual file limits apply: 10 MB per file, 5 GB in total, and at most 30,000 files and directories. There are also limits on read and write activity, expressed as the I/O limit, but those details are complicated and secret.

MySQL storage limits are based on fair use. There are no hard limits on tables, rows, columns or disk space, but there are limits on excessive query use. But you rarely notice the limits if you don’t do anything stupid. And you seem to be performance conscious enough that you won’t do anything stupid.


So in the case of mysql, I should create only one db for this purpose?



Yes. I can’t really think of a situation where you would want more then one database for a single applications on free hosting.


Yes :smiley:


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.