mysql - InnoDB row size large as compared to MyIsam -


I have a table for the column, one small, one integer and two floats. The expected memory for each line is 14bytes (2 + 4 + 2 * 4). There are approximately 700,000 rows in my table. I have not set any primary key and index, whereas MyIsam is about 10MB (15b for each line) Average), the INODAB type takes more than 30 MB (average of 44 B). What am I missing here? Is INODB has too much overhead for each line, or is the position number of the table is not reliable. I need to store data which will run in GBS, so the need to fix the storage type based on the weight of the different parameters is.

Inodb tables take more space compared to MyOzam. Among the features provided by storage access and InnoDB (crash-security, transactions, and foreign keys) is in favor of trade-off IndiBee, even if you have to decide. You have already switched from MyisAM to InnoDB, I will not go back.

It is worth noting that if you go ahead and use the InDB, then you definitely want to define a primary key (and ideally small). See the way this is due to InnoDB wrt storage and other index behavior.


Comments