# MySQL 5.7 - some .IBD files 15% smaller on master than on slaves **URL:** \ **Category:** MySQL & MariaDB\ **Created:** [May 30, 2023, 9:30pm UTC](https://forums.percona.com/t/mysql-5-7-some-ibd-files-15-smaller-on-master-than-on-slaves/22400 "2023-05-30T21:30:03Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [May 31, 2023, 7:35pm UTC](https://forums.percona.com/t/mysql-5-7-some-ibd-files-15-smaller-on-master-than-on-slaves/22400/7 "2023-05-31T19:35:37Z")
Have a look at this recent post and Yves’s answer. > [@Disk Divergence across Master and Slaves](https://forums.percona.com/t/disk-divergence-across-master-and-slaves/14022/14): > > So, InnoDB stores rows in b-trees. Pages in a b-tree can be anywhere between half filled (50%) and filled (100%). Let’s assume there is a long running read query running on the replica forcing a consistent read view to stay opened. A row is deleted from an innodb page and another one is later inserted to the same page. The page in question is almost full. Since there is no long running query on the master, the old rows is removed by the purge thread almost immediately and then the new row is ad… --- _[View the full topic](https://forums.percona.com/t/mysql-5-7-some-ibd-files-15-smaller-on-master-than-on-slaves/22400)._