Demo Data from EDBT 2026 / reviewers in the wild / expert
Helge Brügner
dblp:198/6794
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2017
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1
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 |
Memory systems · 77% Storage systems · 12% Distributed systems · 12% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Operating systems › persistence
crash consistency |
0.3 | 1 | 2017 | NVthreads: Practical Persistence for Multi-threaded Applications · EuroSys 2017 |
Memory systems
non-volatile memory |
0.3 | 1 | 2017 | NVthreads: Practical Persistence for Multi-threaded Applications · EuroSys 2017 |
Memory systems › non-volatile memory › persistent memory
persistent memory programming |
0.3 | 1 | 2017 | NVthreads: Practical Persistence for Multi-threaded Applications · EuroSys 2017 |
Distributed systems › fault tolerance › failure models
crash failures |
0.1 | 1 | 2017 | NVthreads: Practical Persistence for Multi-threaded Applications · EuroSys 2017 |
Storage systems
storage reliability |
0.1 | 1 | 2017 | NVthreads: Practical Persistence for Multi-threaded Applications · EuroSys 2017 |
Methods — techniques the papers use, named apart from their topics
thread-level persistence · 0.6non-volatile memory persistence · 0.6
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2017 | NVthreads: Practical Persistence for Multi-threaded ApplicationsabstractNon-volatile memory technologies, such as memristor and phase-change memory, will allow programs to persist data with regular memory instructions. Liberated from the overhead to serialize and deserialize data to storage devices, programs can aim for high performance and still be crash fault-tolerant. Unfortunately, to leverage non-volatile memory, existing systems require hardware changes or extensive program modifications. Terry Ching-Hsiang Hsu, Helge Brügner, Indrajit Roy 0001, Kimberly Keeton, Patrick Eugster |
EuroSys | 2 |