Quote:
Originally Posted by CHMOD
That is what I always tell to my customers who are sick of CCBill's slow stats:
Parsing a database of 100's and 100's gigs of data takes time.
|
It does most of the time. So then you add "PARTITION BY" to a couple of the table definitions and it runs literally a hundred times faster. Twitter has 140 million users and a billion tweets and their MySQL database isn't slow. Just because most large databases are slow doesn't mean they have to be. Wikipedia uses a very large MySQL database and it isn't slow. Youtube's pages aren't slow, and they come from a MySQL database.
A few simple changes could make CCBill's database a thousand times faster, they just need to contract a database person to do it. In house techs have convinced management to go with a data warehouse and while that may be a good idea, there's no reason the MySQL side should be slow. Their database isn't bigger than Youtube or Twitter.
Google's database is petabytes and while it's not running MySQL for the most part, it gives you results as you type the query.
I hope the CCBill devs have looked at:
http://www.pcworld.com/businesscenter/article/253489/twitter_releases_its_mysql_scalability_tweaks.html