Forum Moderators: phranque
I have had a new system implemented where a page lists widgets along with their details, and on the same page it has a column that lists links to 'other nearby widgets' and 'other nearby towns' that sell widgets, along with distance calculations. All this information is retrieved from database, so i guess thats a lot to handle? Most pages have to access several tables. The town table currently holds details for around 58339 towns AND widgets. Would this table be better split up?
Someone mentioned using flatfiles to speed things up. Are there any database design/optimisation experts out there? Please sticky me for url's if you can help or advise.
Many thanks,
chrisandsar
I wouldnt know. I payed someone to do the database work a while back. I dont 'think' there are any, just tables containing all the data. e.g TownTable contains fields: townID, description, location, grid reference etc etc. There is however a table that gives object ID's (one of the objects being a town). maybe this is what you mean by an index?
Sorry, this is why i need an expert to contact me and maybe agree to take a look
Personally, I wouldn't have mixed widgets with town data, but that is just for orginazational purposes.
To answer your question, MySQL can handle 60k rows in a table just fine. It all depends on how your queries are structured and how your indexes are setup.
I run several websites with databases ranging from 600k to 4 million rows per table and all but the most complex queries are returned within 0-2 seconds.
many thanks
