Re: Best practice in this situation?
Posted by: Rick James
Date: July 26, 2011 11:18PM

Yes, you are not threatening MySQL's _physical_ limits. But you could be in for some performance struggles.

The largest table I have seen on these forums had 6645 million rows. 500M rows is at the 99th percentile. Tables that big have performance problems because not much of the data/indexes can be cached, thereby leading to a lot of disk I/O. Often there are ways to work around the performance problems, but you should probably look into them as soon as you have a good feel for what you would _like_ for
* SHOW CREATE TABLE.
* SELECTs. (to see what indexes are needed, etc)
* How the data will flow into the table(s). (At that size, even the INSERTs and UPDATEs are potential performance bottlenecks.)
* Whether you will be purging data. (Huge DELETEs are a performance snag, but there is (usually) a simple workaround.)

For InnoDB, there is a limit of 64TB of data+index. You are looking at under 1TB, correct?

Options: ReplyQuote


Subject
Written By
Posted
Re: Best practice in this situation?
July 26, 2011 11:18PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.