EDBT 2026 Demo / reviewers in the wild / expert
Neil Kaushikkar
dblp:434/0840
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2026
0009-0005-9745-0626ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1 · 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
1 paper |
Storage systems · 44% Memory systems · 44% Distributed systems · 13% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Memory systems
cache management |
1.0 | 1 | 2026 | A Logically Disaggregated Cache for Replicated Storage Systems · EuroSys 2026 |
Storage systems
distributed storage |
1.0 | 1 | 2026 | A Logically Disaggregated Cache for Replicated Storage Systems · EuroSys 2026 |
Distributed systems
replication |
0.3 | 1 | 2026 | A Logically Disaggregated Cache for Replicated Storage Systems · EuroSys 2026 |
Methods — techniques the papers use, named apart from their topics
online analysis · 1.0cache demotion · 1.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2026 | A Logically Disaggregated Cache for Replicated Storage SystemsabstractWe study if replicated storage systems effectively utilize the caches embedded within each replica. Our study reveals that existing systems manage the embedded caches in each replica in silos, leading to significant cache redundancy across replicas and consequently low performance. To address this problem, we introduce logically disaggregated cache (Ldc), a new approach to managing caches in replicated storage systems. Ldc disaggregates the embedded caches from the replicas to form a single, logical cache. Ldc then allows any replica to access any part of the logical cache, which reduces redundancy caused by reads. Because writes pollute all caches, Ldc quickly demotes written objects to limit redundancy caused by writes. Ldc, however, realizes that reducing redundancy may hurt performance in some cases and thus employs an online analyzer to strike a balance between cache redundancy and coverage. We implement Ldc in three systems: an eventually-consistent KV store, a strongly-consistent KV store, and a production database. Using microbenchmarks, macrobenchmarks, and real-world traces, we show that the Ldc versions perform significantly better than the original systems (e.g., 2.6× to 5.4× higher throughput in the eventually-consistent KV store under YCSB). Kiran Hombal, Henry Zhu, Shreesha G. Bhat, Neil Kaushikkar, Ramnatthan Alagappan, Aishwarya Ganesan |
EuroSys | 4 |