Optimizing MySQL Database structure for big big data

[eluser]Sean Murphy[/eluser]
I agree with Crafter, creating a database for each entry doesn't sound like it would scale well even for a very small site. Not, a good idea.

Are you thinking of sharding, or table partitioning? These techniques are sometimes used to increase performance on incredibly large sites (YouTube, Digg, etc.), but I doubt you'd need to worry about it.

I think you'd have better success optimizing your queries and storage engines. Also, if you're constantly joining on the same tables, you might try de-normalizing your schema where you can.

Hope that helps!