Am I underestimating MySQL?

Question

I'm going to implement a feature on my website that recommends content to users based on the content that they already have in their library (a la Last.fm). A single table stores all records of added content, so the row may look something like this:

--------------------
| userid | content |
--------------------
|   28   |    a    |
--------------------

When I want to recommend some content to a user, I use a query to get all user IDs that have content added to their library. Then, from these user IDs, I make another request that finds the next most common content among these users (fx. 'B') and shows it to the user.

My problem is when I think of the big picture here. Say that in the end, my site will hold something like 500,000 rows in a table, will it be very slow, or am I underestimating MySQL here?

Answer 1

You won't know about it until you test it, so start prototyping.

As a rule, 500,000 lines cost almost nothing. I am a little worried when my tables reach 50 million because it takes a while when I have to clear old data, although data queries are still fast.

, . , 50 , , , 50 000 50 , . , , / mysql.

Answer 2

500 000 , . , .

Answer 3

:

, MySQL , 500 000 ?

- .

Answer 4

. , , , .

Answer 5

500.000 - Foxpro - 10 ;) . , ;)

Answer 6

: , MySQL (, , ). 500 . , , , .

, nos , , , ; (50 - , , ), , , .

: 500 .? . 50 ? .

Answer 7

, , , ( ), .

500k - , . , , 500 . * 500 . * 500 . , .