Concurrent operations on \(B^ *\)-trees with overtaking (Q579974): Difference between revisions

From MaRDI portal
Set OpenAlex properties.
ReferenceBot (talk | contribs)
Changed an Item
 
Property / cites work
 
Property / cites work: Organization and maintenance of large ordered indexes / rank
 
Normal rank
Property / cites work
 
Property / cites work: Concurrency of operations on B-trees / rank
 
Normal rank
Property / cites work
 
Property / cites work: Concurrent search and insertion in 2-3 trees / rank
 
Normal rank
Property / cites work
 
Property / cites work: Concurrent manipulation of binary search trees / rank
 
Normal rank
Property / cites work
 
Property / cites work: A New Method for Concurrency in B-Trees / rank
 
Normal rank
Property / cites work
 
Property / cites work: Efficient locking for concurrent operations on B-trees / rank
 
Normal rank
Property / cites work
 
Property / cites work: B-trees in a system with multiple users / rank
 
Normal rank
Property / cites work
 
Property / cites work: Q3347338 / rank
 
Normal rank

Latest revision as of 12:15, 18 June 2024

scientific article
Language Label Description Also known as
English
Concurrent operations on \(B^ *\)-trees with overtaking
scientific article

    Statements

    Concurrent operations on \(B^ *\)-trees with overtaking (English)
    0 references
    0 references
    1986
    0 references
    Algorithms for concurrent operations (i.e., searches, insertions, and deletions) on \(B^*\)-trees are presented. These algorithms improve those given by \textit{P. L. Lehman} and \textit{S. B. Yao} [ACM Trans. Database Syst. 6, 650-670 (1981; Zbl 0465.68061)] since an insertion process has to lock only one node at any time (as opposed to locking simultaneously two or three nodes in ibid. Another improvement is the ability to compress the tree when some nodes become too sparse as a result of some deletions. Compressing the tree is done by a process that periodically scans the whole tree while running concurrently with the other operations. Alternatively, it is possible to initiate a compression process after each deletion that leaves a node less than half full. These compression processes may run concurrently with the other operations, and they scan only the nodes that have to be compressed. Each compression process has to lock simultaneously three nodes.
    0 references
    0 references
    0 references
    0 references
    0 references
    data structure
    0 references
    databases
    0 references
    concurrent operations
    0 references
    searches
    0 references
    insertions
    0 references
    deletions
    0 references
    \(B^ *\)-trees
    0 references
    compression
    0 references
    0 references