Hi,
From what I can measure we get only the 70% filling.
The data is sorted in ascending order,
however there is a catch in the sense that the first colummn consist of
all identical variables (this is kept to maintain some consistency with
our organization),
and thus we have set the primary ke
Hi!
Sorry, InnoDB does not have key compression.
Every row has a 6-byte trx id, a 7-byte roll ptr, and
a header of 6 bytes. In addition, every field uses
1 byte as a pointer to it.
Calculating:
180 million x (6 + 7 + 6 + 2 + 4) bytes = 4.5 GB
Since every page is filled only 15/16 full even if
Sander Pilon wrote:
>Lose (some of) the keys!? Keys, especially on small rows (where a key
>introduces a lot of overhead), can take a significant percentage of
>space.
>
>Turn on key compression? (dunno if innodb supports that)
>
>Other then that I wouldn't know. But live with the fact that keys
Lose (some of) the keys!? Keys, especially on small rows (where a key
introduces a lot of overhead), can take a significant percentage of
space.
Turn on key compression? (dunno if innodb supports that)
Other then that I wouldn't know. But live with the fact that keys
introduce overhead. It will
