Database Records

@Sinnbeck so it means mostly the performance of the system depends on the performance of the servers hardware and it doesn't depends of the how much record we have ?

@shadkamel the more records the slower it is. But what I am saying is to not spend 3 weeks trying to get the database to be fast with 3 million records. Maybe you never hit 3 million records at all. And maybe things are different when you do. Or you know your data better and can find a better solution

@Sinnbeck actually there is a project in my mind that can have a huge amount of data, i want to know what that ways that could solve my problem. indexes and server upgrade are one of the choices, what else we have please ?

@shadkamel Like @sinnbeck, you needn't worry about that just yet, make the app work first then when you are rolling hire a database person.

Start at one.

1. Have a good database model
2. Have the proper indexes (not too many, not too few), use explain to find out which columns should have them
3. Clean out old data, either delete it or move to one or more archive tables.
4. Use views where proper to decrease the amount of data read.
5. Read only what you need.
6. Paginate from the database.
7. Never filter or sort in php, let the database handle all that.
8. Partition your tables.
9. Get more ram and CPU for your database host.
10. Move to clustered databases.

@shadkamel the key word is "can"

"i have an idea for a company that drivers delivers burgers all over the world. It could have 50000 trucks. How should I structure my company to manage that many trucks?"

The answer is you don't. You start out maybe planning for 50 trucks and build up as you go

i thing that was what i wanted, thank you very much for you two both @sinnbeck @tray2.