Demo Data from SIGIR 2026 / reviewers in the wild / expert
Seongho Lee
dblp:355/8578
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2023
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Computer networks · 1 · 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
1 paper |
Storage systems · 50% Cloud and datacenter computing · 50% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Storage systems › networked storage › storage networking
remote flash access |
0.7 | 1 | 2023 | i-NVMe: Isolated NVMe over TCP for a Containerized Environment · INFOCOM 2023 |
Operating systems › resource management
resource scheduling |
0.2 | 1 | 2023 | i-NVMe: Isolated NVMe over TCP for a Containerized Environment · INFOCOM 2023 |
Methods — techniques the papers use, named apart from their topics
traffic-based charging · 1.3CPU throttling · 1.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2023 | i-NVMe: Isolated NVMe over TCP for a Containerized EnvironmentabstractNon-Volatile Memory Express (NVMe) over TCP is an efficient technology for accessing remote Solid State Drives (SSDs); however, it may cause a serious interference issue when used in a containerized environment. In this study, we propose a CPU isolation scheme for NVMe over TCP in such an environment. The proposed scheme measures the CPU usage of the NVMe over TCP worker, charges it to containers in proportion to their NVMe traffic, and schedules containers to ensure isolated sharing of the CPU. However, because the worker runs with a higher priority than normal containers, it may not be possible to achieve CPU isolation with container scheduling alone. To solve this problem, we also control the CPU usage of the worker by throttling NVMe over TCP traffic. The proposed scheme is implemented on a real testbed for evaluation. We perform extensive experiments with various workloads and demonstrate that the scheme can provide CPU isolation even in the presence of excessive NVMe traffic. Seongho Lee, Ikjun Yeom |
INFOCOM | 1 |