I am in the process of architecting and pretty soon, developing an online delivery system.
My First Dilema:
Basically I will have a number or users, each managing a customizable list of items. These items/objects are all identical in structure and form. I estimate the average number of items at +/-100 items per user; the number of users initially at about 100+ (10,000+ items initially) with a high possibility of that number growing in excess of 3000+ users... each managing +/- 100 items. This means a headroom of 300,000+ items total.
At the moment, I am inclined to create a new table for every new user, as I am skeptical whether it would make any sense at all to throw all the items in one ITEMS table... and whether mySQL would perform optimally with a table that size. However I want to make sure I cover all my bases and get any aditional feedback to confirm my design decisions.
On my last project the mySQL tables averaged 5000+ records, which mySQL handled pretty well once indexed.
What are your thoughts, experiences, and insights as far as practical limits you've encountered with mySQL on some of your projects? Thanks... any feedback greatly appreciated.
Blax
