16 reputation
2
bio website
location
age
visits member for 3 years, 4 months
seen Jul 21 '11 at 12:25

Mar
8
awarded  Popular Question
Jul
21
comment Different MySQL Datafile Sizes After Restoration
Thanks for all your info. I will study this changes in test environment.
Jul
21
comment Different MySQL Datafile Sizes After Restoration
The application mainly does INSERTing in 3 tables: the first one is in PRIMARY KEY order, but the PRIMARY KEY of the other 2 is a HASH of the line inserted in the first table, so is almost never in correct order. So I bet there is a lot of fragmentation and poorly used blocks due to these tables... Isn't supposed an optimization tool to be designed for this scenario? I would say that an optimization tool should do it most in this case. Maybe it has defragmented ibdata, but it has increased the number of blocks used! (from 3.6GiB to 5.3GiB, in 16KiB blocks: something like 100,000 extra blocks).
Jul
21
comment Different MySQL Datafile Sizes After Restoration
I understand that this method would shrink ibdata by spreading this data in different files, thus making the total amount equivalent to the size of the previous ibdata. Am I wrong?
Jul
19
comment Different MySQL Datafile Sizes After Restoration
hello, thanks for your quick answer. Our database is already InnoDB. I've optimized the restored databased (mysqlcheck -o --all-databases) and its ibdata file has increased from 3.6GiB to 5.3GiB (the same size as the master's ibdata). Why does it expands ibdata? How can I test if mysqlcheck would remove unused space within production's ibdata without making any real change?
Jul
19
awarded  Student
Jul
19
asked Different MySQL Datafile Sizes After Restoration