Demo Data from EDBT 2026 / reviewers in the wild / expert
Vito Kortbeek
dblp:260/5481
· DBLP profile ↗
3ranked-venue papers
2as first author
2since 2021 · last 2025
0000-0001-7480-8422ORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3 · 2 first-author · 2 since 2021Systems, architecture and hardware · 2 · 1 first-author · 1 since 2021
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
3 papers |
Embedded and real-time systems · 39% Memory systems · 32% Distributed systems · 24% | |
| Software engineering, system software, and programming languages
2 papers |
Compilers and program optimization · 82% Operating systems · 18% |
Topics — the 9 heaviest of 9, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Embedded and real-time systems
intermittent computing |
1.9 | 3 | 2025 | Data Cache for Intermittent Computing Systems with Non-Volatile Main Memory · ASPLOS (2) 2025 WARio: efficient code generation for intermittent computing · PLDI 2022 Time-sensitive Intermittent Computing Meets Legacy Software · ASPLOS 2020 |
Memory systems
non-volatile memory |
1.0 | 2 | 2025 | Data Cache for Intermittent Computing Systems with Non-Volatile Main Memory · ASPLOS (2) 2025 WARio: efficient code generation for intermittent computing · PLDI 2022 |
Distributed systems › fault tolerance
checkpointing |
0.9 | 1 | 2025 | Data Cache for Intermittent Computing Systems with Non-Volatile Main Memory · ASPLOS (2) 2025 |
Memory systems › cache › CPU cache
data cache |
0.9 | 1 | 2025 | Data Cache for Intermittent Computing Systems with Non-Volatile Main Memory · ASPLOS (2) 2025 |
Compilers and program optimization › program transformation
compiler transformations |
0.6 | 1 | 2022 | WARio: efficient code generation for intermittent computing · PLDI 2022 |
Distributed systems › fault tolerance › checkpointing
checkpoint placement |
0.6 | 1 | 2022 | WARio: efficient code generation for intermittent computing · PLDI 2022 |
Embedded and real-time systems
energy harvesting systems |
0.4 | 1 | 2020 | Time-sensitive Intermittent Computing Meets Legacy Software · ASPLOS 2020 |
Energy-efficient computing
energy harvesting |
0.3 | 1 | 2025 | Data Cache for Intermittent Computing Systems with Non-Volatile Main Memory · ASPLOS (2) 2025 |
Operating systems › fault tolerance
checkpoint and rollback |
0.1 | 1 | 2020 | Time-sensitive Intermittent Computing Meets Legacy Software · ASPLOS 2020 |
Methods — techniques the papers use, named apart from their topics
compiler analysis · 1.1write-after-read detection · 0.9checkpointing · 0.9programming abstractions · 0.4programming abstraction · 0.4
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Data Cache for Intermittent Computing Systems with Non-Volatile Main MemoryabstractIntermittently-operating embedded computing platforms powered by energy harvesting must frequently checkpoint their computation state. Using non-volatile memory reduces checkpoint size by eliminating the need to checkpoint volatile memory but increases checkpoint frequency to cover Write After Read (WAR) dependencies. Additionally, non-volatile memory is significantly slower to access - while consuming more energy than its volatile counterpart - suggesting the use of a data cache. Unfortunately, existing data cache solutions do not fit the challenges of intermittent computing and often require additional hardware or software to detect WARs. In this paper, we extend the data cache by integrating it with WAR detection - dropping the need for an additional memory tracker. This idea forms the basis of NACHO: a data cache tailored to intermittent computing. NACHO, on average, reduces intermittent computing runtime overhead by 54% compared to state of the art cache-based systems. It also reduces the number of non-volatile memory writes by 82% compared to a data cache-less system, and 18% on average compared to multiple state of the art cache-based systems. Sourav Mohapatra, Vito Kortbeek, Marco Antonio van Eerden, Jochem Broekhoff, Saad Ahmed, Przemyslaw Pawelczak |
ASPLOS (2) | 2 |
| 2022 | WARio: efficient code generation for intermittent computingabstractIntermittently operating embedded computing platforms powered by energy harvesting require software frameworks to protect from errors caused by Write After Read (WAR) dependencies. A powerful method of code protection for systems with non-volatile main memory utilizes compiler analysis to insert a checkpoint inside each WAR violation in the code. However, such software frameworks are oblivious to the code structure---and therefore, inefficient---when many consecutive WAR violations exist. Our insight is that by transforming the input code, i.e., moving individual write operations from unique WARs close to each other, we can significantly reduce the number of checkpoints. This idea is the foundation for WARio: a set of compiler transformations for efficient code generation for intermittent computing. WARio, on average, reduces checkpoint overhead by 58%, and up to 88%, compared to the state of the art across various benchmarks. Vito Kortbeek, Souradip Ghosh, Josiah D. Hester, Simone Campanoni, Przemyslaw Pawelczak |
PLDI | 1 |
| 2020 | Time-sensitive Intermittent Computing Meets Legacy SoftwareabstractTiny energy harvesting sensors that operate intermittently, without batteries, have become an increasingly appealing way to gather data in hard to reach places at low cost. Frequent power failures make forward progress, data preservation and consistency, and timely operation challenging. Unfortunately, state-of-the-art systems ask the programmer to solve these challenges, and have high memory overhead, lack critical programming features like pointers and recursion, and are only dimly aware of the passing of time and its effect on application quality. We present Time-sensitive Intermittent Computing System (TICS), a new platform for intermittent computing, which provides simple programming abstractions for handling the passing of time through intermittent failures, and uses this to make decisions about when data can be used or thrown away. Moreover, TICS provides predictable checkpoint sizes by keeping checkpoint and restore times small and reduces the cognitive burden of rewriting embedded code for intermittency without limiting expressibility or language functionality, enabling numerous existing embedded applications to run intermittently. Vito Kortbeek, Kasim Sinan Yildirim, Abu Bakar, Jacob Sorber, Josiah D. Hester, Przemyslaw Pawelczak |
ASPLOS | 1 |