I spend the last couple days playing with InnoDB page compression
on the latest Percona build.
I’m pretty happy so far with Percona and the latest InnoDB
changes.
Compression wasn’t living up to my expectations though.
I think the biggest problem is that the compression can only use
one core in replication and ALTER TABLE statements.
We have an 80GB database that was running on 96GB boxes filled
with RAM.
I wanted to try to run this on much smaller instances (32GB-48GB
boxes) by compressing the database.
Unfortunately, after 24 hours of running an ALTER TABLE which
would only use one core per table, the SQL replication thread
went to 100% and started falling behind fast.
I think what might be happening is that the InnoDB page buffer is
full because it can’t write to the disk fast enough which causes
the insert thread to force compression of the pages in the
foreground.
…
[Read more]