Demo Data from VLDB 2026 / reviewers in the wild / expert
Yuyangjun Lu
dblp:413/6487
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software 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 |
Storage systems · 56% Embedded and real-time systems · 44% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Storage systems
flash and SSD |
0.9 | 1 | 2025 | A Lightweight I/O Throttling Service to Improve the User Experience of Mobile Devices · IEEE Trans. Serv. Comput. 2025 |
Embedded and real-time systems
mobile computing |
0.9 | 1 | 2025 | A Lightweight I/O Throttling Service to Improve the User Experience of Mobile Devices · IEEE Trans. Serv. Comput. 2025 |
Storage systems › storage performance
i/o latency |
0.3 | 1 | 2025 | A Lightweight I/O Throttling Service to Improve the User Experience of Mobile Devices · IEEE Trans. Serv. Comput. 2025 |
Methods — techniques the papers use, named apart from their topics
i/o compression · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | A Lightweight I/O Throttling Service to Improve the User Experience of Mobile DevicesabstractAs one of the most frequently occurring operations, I/Os significantly affect the application launching time and frame rate of mobile devices, hence influencing the user experience. However, the response speed of I/O requests is still the bottleneck in practice. This paper shows that high I/O latency is usually due to the congestion inside Flash instead of the system layer. Unfortunately, Flash is treated as a black box device and cannot be modified after delivery. In this paper, we propose a novel service to address this issue without an intra-Flash modification. Specifically, this paper proposes a lightweight I/O throttling framework in mobile systems named FlashDAM. This service throttles the I/O flow to make way for I/Os that may block the foreground application. FlashDAM is the first work that proves that proper I/O throttling positively affects the user experience, contrary to the common belief. Furthermore, this paper proposes FlashDAM$^+$, an enhanced version of FlashDAM. By coordinating I/O throttling and compression, FlashDAM's effect in the system layer is minimized. We have implemented FlashDAM on real mobile devices. Experimental results illustrate that the app launching speed and frame rate are enhanced by 72% and 45% separately compared to the state-of-the-art. When enabling the compression feature of FlashDAM, that is, FlashDAM$^+$, screen jank and application launch latency are further reduced by 9.5% and 11.4%, respectively, under heavy background I/O load. Changlong Li 0006, Zongwei Zhu, Yuyangjun Lu, Chao Wang 0003, Xuehai Zhou, Edwin H.-M. Sha |
IEEE Trans. Serv. Comput. | 3 |