Re: ibdata1 file getting huge
Posted by:
Rick James
Date: October 21, 2014 09:57AM
Do
SHOW TABLE STATUS;
Look at Data_free; that will say how much space is 'wasted' in ibdata1. Currently, TRUNCATE and DROP simply add to Data_free without shrinking ibdata1.
If you switched to innodb_file_per_table=1 (which will require dumping and reloading), most of that free space can be recouped. Furthermore, when you TRUNCATE or DROP a table, the space will be immediately recouped.
No, I can't say that this change will definitely help. It depends a lot on what kinds of things you do, and in what order. But it is likely to help.
Subject
Views
Written By
Posted
2564
October 17, 2014 06:57AM
1484
October 18, 2014 12:25PM
1248
October 20, 2014 06:08AM
Re: ibdata1 file getting huge
1232
October 21, 2014 09:57AM
1552
October 25, 2014 01:02AM
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.