\(B\)-trees with inserts and deletes: Why free-at-empty is better than merge-at-half (Q686641)
From MaRDI portal
| This is the item page for this Wikibase entity, intended for internal use and editing purposes. Please use this page instead for the normal view: B-trees with inserts and deletes: Why free-at-empty is better than merge-at-half |
scientific article; zbMATH DE number 428584
| Language | Label | Description | Also known as |
|---|---|---|---|
| default for all languages | No label defined |
||
| English | \(B\)-trees with inserts and deletes: Why free-at-empty is better than merge-at-half |
scientific article; zbMATH DE number 428584 |
Statements
\(B\)-trees with inserts and deletes: Why free-at-empty is better than merge-at-half (English)
0 references
10 October 1993
0 references
\(B\)-trees are a well-known and widely used data structure which allows efficient search in very large databases. A \(B\)-tree of parameter \(p\) is a balanced tree in which the distance between the root and any leaf is the same and any non-leaf mode has between 1 and \(2p-1\) children. The paper investigates the space utilization (i.e. the expected percentage of a node used to store data) under insertions and two policies of deletions: (1) free-at-empty, when a node is deleted when it becomes empty and the deletions are propagated upwards, and (2) merge-at-half, when a node becoming half empty after a deletion is merged with its neighbor. Analytical results are proved and simulation data is reported for these two strategies. The paper provides a simple rule of thumb, depending on the comparative rate of delete vs. insert operations, which indicates when one of the strategy is to be preferred.
0 references
\(B\)-trees
0 references
space utilization
0 references
insertions
0 references
deletions
0 references
0.7973090410232544
0 references
0.7887507677078247
0 references
0.7866936326026917
0 references
0.7866936326026917
0 references
0.7686931490898132
0 references