MySQL Forums
Forum List  »  Partitioning

Re: Help me to design this Mysql production database (with very large tables).
Posted by: Rick James
Date: August 27, 2009 09:22PM

Shoveling rows from one table to another can be costly. Are you doing any transformations as you move them?

If nothing is changing, leaving them in a single table will be faster.

What will you do with the data later? Some kind of summarizing SELECT?

To assist in analyzing slow SELECTs, please provide
* SHOW CREATE TABLE tbl\G -- engine, indexes
* SHOW TABLE STATUS LIKE 'tbl'\G -- sizes
* EXPLAIN SELECT ...\G -- clues of inefficiencies
* SHOW VARIABLES LIKE '%buffer%'; -- cache size
and surround them with [ code ] and [ / code ]

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Help me to design this Mysql production database (with very large tables).
2309
August 27, 2009 09:22PM


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.