In my last post about big MySQL deployments, I am quickly mentioning that InnoDB compression is allowing dividing disk usage by about 4.3 on a 200+ TiB dataset. In this post, I will give more information about this specific use case of InnoDB table compression and I will share some statistics and learnings on this system and subject. Note that I am not covering InnoDB page compression which is a new feature of MySQL 5.7 (also known as hole punching).
Showing posts with label MyRocks. Show all posts
Showing posts with label MyRocks. Show all posts
Monday, August 7, 2017
Monday, May 22, 2017
Better Replication when running both InnoDB and MyRocks (or other Storage-Engines)
Kristian Nielsen is working on a new feature for MariaDB 10.3 and he published very interesting results. This feature is MDEV-12179: Per-engine mysql.gtid_slave_pos tables. He writes about replicating twice as fast in the worst case when using two storage engines (InnoDB and MariaRocks in his tests, but could also be InnoDB and TokuDB or TokuDB and MyRocks). I will let you read all the details on his blog about Improving replication with multiple storage engines.
Why am I posting this here ? Mostly because I want to share with you that:
Why am I posting this here ? Mostly because I want to share with you that:
- I am also involved in this project,
- I am working closely with Kristian on this feature,
- and that Booking.com is financing Kristian's time on this development.
Subscribe to:
Posts (Atom)