Click here to Skip to main content
15,917,875 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
If the records are inserted in ascending order(usually primary key is auto-increment),so each split will cause the old leaf half-full.Since the records are inserted in ascending order,so the later records will be insert into the new leaf node until the next split.Old leaf node will keep half-full state.
Actually a logical node is equal to a physical page in innodb.So if the half-full page cause a waste of storage space?

What I have tried:

read reference:
b+tree split:Wiki B+ tree
innodb b+ tree index structure:B+Tree index structures in InnoDB - Jeremy Cole
Posted
Updated 18-Jan-18 19:14pm

1 solution

Generally B+tree nodes are about ~65%-75% full on average, and yes they are not all full that is by design.

As for wasted space, that really depends on how the page is written to disk, but potentially there is some "waste".
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900