I have an innodb table with 3 columns, int(11), bigint(20) and decimal(24,5). Based on what I see in the docs each row should account for 24 bytes.
Currently this table has 25923814 rows in it (generated from select count() from table), therefore I would think that the amount of data should add up to @ 600MB (24numrows).
However, the data length that I get from information_schema.tables is 2718744576 (roughly 2.5GB). This table was analyzed very recently as well.
Could someone point me to a doc or explain what is going on here? The table is very static, its lifetime consists of a bunch of inserts, truncation then more inserts and truncation.
Any ideas on how I can create a sizing calculation that is more accurate?
The table is using utf8, but I would not think that has anything to do with the sizing. Haven’t tested that theory yet, but I would think that it wouldn’t matter what char set I use since this table only consists of numbers.
I am running 64 bit mysql 5.5.8 on Solaris 10. Should I be using Percona server instead?