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

From MaRDI portal
Importer (talk | contribs)
Created a new Item
 
Importer (talk | contribs)
Changed an Item
Property / review text
 
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.
Property / review text: 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. / rank
 
Normal rank
Property / Mathematics Subject Classification ID
 
Property / Mathematics Subject Classification ID: 68P20 / rank
 
Normal rank
Property / Mathematics Subject Classification ID
 
Property / Mathematics Subject Classification ID: 68P10 / rank
 
Normal rank
Property / Mathematics Subject Classification ID
 
Property / Mathematics Subject Classification ID: 68P05 / rank
 
Normal rank
Property / zbMATH DE Number
 
Property / zbMATH DE Number: 4016242 / rank
 
Normal rank
Property / zbMATH Keywords
 
data structure
Property / zbMATH Keywords: data structure / rank
 
Normal rank
Property / zbMATH Keywords
 
databases
Property / zbMATH Keywords: databases / rank
 
Normal rank
Property / zbMATH Keywords
 
concurrent operations
Property / zbMATH Keywords: concurrent operations / rank
 
Normal rank
Property / zbMATH Keywords
 
searches
Property / zbMATH Keywords: searches / rank
 
Normal rank
Property / zbMATH Keywords
 
insertions
Property / zbMATH Keywords: insertions / rank
 
Normal rank
Property / zbMATH Keywords
 
deletions
Property / zbMATH Keywords: deletions / rank
 
Normal rank
Property / zbMATH Keywords
 
\(B^ *\)-trees
Property / zbMATH Keywords: \(B^ *\)-trees / rank
 
Normal rank
Property / zbMATH Keywords
 
compression
Property / zbMATH Keywords: compression / rank
 
Normal rank

Revision as of 18:33, 1 July 2023

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