Architectural of database with millions of searchable records
Posted on 2011-03-22
I am building a comparison site with around 500,000 product with maybe 30 data fields for each product.
I have little experience with something this scale (over a few thousand records), does anyone have any suggestions on how to ensure this is done efficient and how product pictures and files need to be organized for it being most efficient. I can code the logic but worried about efficiency and retrieving records quickly.
Would it be better to break the data into a bunch of tables? Does having a smaller table make it faster to search?
Does an auto suggest code work off directly from the db or some cached file produced elsewhere?