Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Timo Lilja

dblp:19/6158 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2007
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Databases, data mining, and information retrieval
1 paper
Transaction processing and concurrency control · 75% Indexing and storage engines · 25%

Topics — the 3 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Indexing and storage engines
b+-tree
0.112007
Online Bulk Deletion · ICDE 2007
Transaction processing and concurrency control › concurrency control › locking
key-range locking
0.112007
Online Bulk Deletion · ICDE 2007
Transaction processing and concurrency control › concurrency control › locking
multi-granularity locking
0.112007
Online Bulk Deletion · ICDE 2007

Methods — techniques the papers use, named apart from their topics

multi-granular key-range locking · 0.1b-tree rebalancing · 0.1
YearPublicationVenuePosition
2007 Online Bulk Deletion
abstract
We consider online bulk-delete operations on a large database table organized as a primary (sparse) B+-tree index on a multi-attribute key. Using the natural range partitions induced by prefixes of the key, we define a multi-granular key-range locking protocol in which a bulk operation locks a small number of logical fragments of the table covering the target of the operation. We also present an efficient and recoverable bulk-delete algorithm that minimizes the work needed in B-tree rebalancing and in transaction rollback. All the locks needed for a bulk-delete operation are acquired during a scan of the leaf pages covering the target key range; in this scan the records qualifying for deletion are only marked as deleted. The records are physically deleted in a rebalance phase that avoids visiting subtrees in which all records qualify for deletion, thus saving considerably on the number of rebalancing operations.
Timo Lilja, Riku Saikkonen, Seppo Sippu, Eljas Soisalon-Soininen
ICDE1