Demo Data from EDBT 2026 / reviewers in the wild / expert
Heting Li
dblp:164/3610
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2018
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1Software engineering, systems software and programming languages · 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.
| Software engineering, system software, and programming languages
1 paper |
Runtime systems and virtual machines · 50% Programming languages and type systems · 50% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Memory systems · 100% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Runtime systems and virtual machines › virtual machine implementation
java virtual machine |
0.3 | 1 | 2018 | Espresso: Brewing Java For More Non-Volatility with Non-volatile Memory · ASPLOS 2018 |
Memory systems
non-volatile memory |
0.3 | 1 | 2018 | Espresso: Brewing Java For More Non-Volatility with Non-volatile Memory · ASPLOS 2018 |
Memory systems › non-volatile memory › persistent memory
persistent heap |
0.3 | 1 | 2018 | Espresso: Brewing Java For More Non-Volatility with Non-volatile Memory · ASPLOS 2018 |
Methods — techniques the papers use, named apart from their topics
persistent heap design · 0.7crash consistency · 0.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2018 | Espresso: Brewing Java For More Non-Volatility with Non-volatile MemoryabstractFast, byte-addressable non-volatile memory (NVM) embraces both near-DRAM latency and disk-like persistence, which has generated considerable interests to revolutionize system software stack and programming models. However, it is less understood how NVM can be combined with managed runtime like Java virtual machine (JVM) to ease persistence management. This paper proposes Espresso, a holistic extension to Java and its runtime, to enable Java programmers to exploit NVM for persistence management with high performance. Espresso first provides a general persistent heap design called Persistent Java Heap (PJH) to manage persistent data as normal Java objects. The heap is then strengthened with a recoverable mechanism to provide crash consistency for heap metadata. Espresso further provides a new abstraction called Persistent Java Object (PJO) to provide an easy-to-use but safe persistence programming model for programmers to persist application data. Evaluation confirms that Espresso significantly outperforms state-of-art NVM support for Java (i.e., JPA and PCJ) while being compatible to data structures in existing Java programs. Mingyu Wu 0001, Ziming Zhao 0003, Heting Li, Haibo Chen 0001, Binyu Zang, Haibing Guan |
ASPLOS | 4 |