It is well known fact that InnoDB standard page size is 16K or 16384 bytes. Sometime ago we added feature to Percona Server to change that to 4K or 8K (innodb_page_size). That maybe useful for SSD that operates with 4K blocks and you can get really much better throughput with 4K ( however we need to run benchmarks yet to see real effect from it).
The bigger limitation is that this setting is for whole database instance and you need to mysqldump your data, re-create database and load data.
It could be much better if we are able to set it per table, or even per index level – this is what we want to look into in near future.
Another area for improvements: support 32K and 64K pages. Why this is needed ? For InnoDB compression.
Right now if you use 16K and trying to compress, the only good choice is to compress to 8K pages (which gives you only 2:1 compress ratio), and you rarely will be able to compress to 4K.
However I think with 32K and 64K we should be able to compress to 8K and to 16K easily and get 4:1 compression rate, as we will be operate with bigger block size with more possibilities to compress (of course it is workload depended). This is also in our plans.
Having 4K-64K block sizes with ability to set parameter per table and per index would make InnoDB really flexible for different type of use cases and storage. As Oracle makes a lot of new good features in MySQL 5.6, I would like to see that implemented also.
Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.
Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below.