Demo Data from EDBT 2026 / reviewers in the wild / expert
Blaise Sanouillet
dblp:314/7082
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2022
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1 · 1 since 2021Software engineering, systems software and programming languages · 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 |
Memory systems · 56% Cloud and datacenter computing · 44% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Operating systems › resource management › memory management
kernel memory management |
0.6 | 1 | 2022 | TMO: transparent memory offloading in datacenters · ASPLOS 2022 |
Cloud and datacenter computing › resource management
datacenter memory management |
0.6 | 1 | 2022 | TMO: transparent memory offloading in datacenters · ASPLOS 2022 |
Memory systems
memory offloading |
0.6 | 1 | 2022 | TMO: transparent memory offloading in datacenters · ASPLOS 2022 |
Memory systems
non-volatile memory |
0.2 | 1 | 2022 | TMO: transparent memory offloading in datacenters · ASPLOS 2022 |
Methods — techniques the papers use, named apart from their topics
real-time resource shortage measurement · 1.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2022 | TMO: transparent memory offloading in datacentersabstractThe unrelenting growth of the memory needs of emerging datacenter applications, along with ever increasing cost and volatility of DRAM prices, has led to DRAM being a major infrastructure expense. Alternative technologies, such as NVMe SSDs and upcoming NVM devices, offer higher capacity than DRAM at a fraction of the cost and power. One promising approach is to transparently offload colder memory to cheaper memory technologies via kernel or hypervisor techniques. The key challenge, however, is to develop a datacenter-scale solution that is robust in dealing with diverse workloads and large performance variance of different offload devices such as compressed memory, SSD, and NVM. This paper presents TMO, Meta’s transparent memory offloading solution for heterogeneous datacenter environments. TMO introduces a new Linux kernel mechanism that directly measures in realtime the lost work due to resource shortage across CPU, memory, and I/O. Guided by this information and without any prior application knowledge, TMO automatically adjusts how much memory to offload to heterogeneous devices (e.g., compressed memory or SSD) according to the device’s performance characteristics and the application’s sensitivity to memory-access slowdown. TMO holistically identifies offloading opportunities from not only the application containers but also the sidecar containers that provide infrastructure-level functions. To maximize memory savings, TMO targets both anonymous memory and file cache, and balances the swap-in rate of anonymous memory and the reload rate of file pages that were recently evicted from the file cache. TMO has been running in production for more than a year, and has saved between 20-32% of the total memory across millions of servers in our large datacenter fleet. We have successfully upstreamed TMO into the Linux kernel. Johannes Weiner, Niket Agarwal, Dan Schatzberg, Leon Yang, Hao Wang 0011, Blaise Sanouillet, Bikash Sharma, Tejun Heo, Chunqiang Tang, Dimitrios Skarlatos 0002 |
ASPLOS | 6 |