Demo Data from VLDB 2026 / reviewers in the wild / expert
Avner Elizarov
dblp:235/2572
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2019
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 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.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Parallel and multicore computing · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Concurrent programming · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Concurrent programming
concurrent data structures |
0.4 | 1 | 2019 | LOFT: lock-free transactional data structures · PPoPP 2019 |
Parallel and multicore computing › transactional memory
contention management |
0.4 | 1 | 2019 | LOFT: lock-free transactional data structures · PPoPP 2019 |
Parallel and multicore computing
transactional memory |
0.4 | 1 | 2019 | LOFT: lock-free transactional data structures · PPoPP 2019 |
Methods — techniques the papers use, named apart from their topics
lock-free synchronization · 0.8helping mechanism · 0.8
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2019 | LOFT: lock-free transactional data structuresabstractConcurrent data structures are widely used in modern multicore architectures, providing atomicity (linearizability) for each concurrent operation. However, it is often desirable to execute several operations on multiple data structures atomically. We present a design of a transactional framework supporting linearizable transactions of multiple operations on multiple data structures in a lock-free manner. Our design uses a helping mechanism to obtain lock-freedom, and an advanced lock-free contention management mechanism to mitigate the effects of aborting transactions. When cyclic helping conflicts are detected, the contention manager reorders the conflicting transactions execution allowing all transactions to complete with minimal delay. To exemplify this framework we implement a transactional set using a skip-list, a transactional queue, and a transactional register. We present an evaluation of the system showing that we outperform general software transactional memory, and are competitive with lock-based transactional data structures. Avner Elizarov, Guy Golan-Gueta, Erez Petrank |
PPoPP | 1 |