Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

Jiatang Zhou

dblp:411/0909 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
2since 2021 · last 2025
0009-0004-5420-9579ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 2 · 1 first-author · 2 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.

Software engineering, system software, and programming languages
2 papers
Operating systems · 100%
Databases, data mining, and information retrieval
2 papers
Transaction processing and concurrency control · 77% Database system architecture and tuning · 23%

Topics — the 4 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Operating systems › resource management › process management
CPU scheduling
1.722025
Analytics Are Heavy. The DBMS Is Busy. When Will My Mission-Critical Transaction Start Running? · Proc. VLDB Endow. 2025
Low-Latency Transaction Scheduling via Userspace Interrupts: Why Wait or Yield When You Can Preempt? · Proc. ACM Manag. Data 2025
Transaction processing and concurrency control › concurrency control
optimistic concurrency control
0.912025
Analytics Are Heavy. The DBMS Is Busy. When Will My Mission-Critical Transaction Start Running? · Proc. VLDB Endow. 2025
Transaction processing and concurrency control
transaction scheduling
0.912025
Low-Latency Transaction Scheduling via Userspace Interrupts: Why Wait or Yield When You Can Preempt? · Proc. ACM Manag. Data 2025
Operating systems › resource management › process management › CPU scheduling
preemptive scheduling
0.912025
Analytics Are Heavy. The DBMS Is Busy. When Will My Mission-Critical Transaction Start Running? · Proc. VLDB Endow. 2025

Methods — techniques the papers use, named apart from their topics

userspace interrupts · 3.5user-interrupt-assisted context switching · 1.7preemption · 1.7context switching · 1.7
YearPublicationVenuePosition
2025 Low-Latency Transaction Scheduling via Userspace Interrupts: Why Wait or Yield When You Can Preempt?
abstract
Traditional non-preemptive scheduling can lead to long latency under workloads that mix long-running and short transactions with varying priorities. This occurs because worker threads tend to monopolize CPU cores until they finish processing long-running transactions. Thus, short transactions must wait for the CPU, leading to long latency. As an alternative, cooperative scheduling allows for transaction yielding, but it is difficult to tune for diverse workloads. Although preemption could potentially alleviate this issue, it has seen limited adoption in DBMSs due to the high delivery latency of software interrupts and concerns on wasting useful work induced by read-write lock conflicts in traditional lock-based DBMSs. In this paper, we propose PreemptDB, a new database engine that leverages recent userspace interrupts available in modern CPUs to enable efficient preemptive scheduling. We present an efficient transaction context switching mechanism purely in userspace and scheduling policies that prioritize short, high-priority transactions without significantly affecting long-running queries. Our evaluation demonstrates that PreemptDB significantly reduces end-to-end latency for high-priority transactions compared to non-preemptive FIFO and cooperative scheduling methods.
Kaisong Huang, Jiatang Zhou, Zhuoyue Zhao 0001, Dong Xie 0001, Tianzheng Wang 0001
Proc. ACM Manag. Data2
2025 Analytics Are Heavy. The DBMS Is Busy. When Will My Mission-Critical Transaction Start Running?
abstract
Conventional non-preemptive scheduling strategies struggle to meet the latency requirements of mixed workloads: low-priority, long-running analytics can dominate CPU cores while short, high-priority transactions wait a long time to be scheduled. Although preemptive scheduling appears to be a natural solution, it has long been discouraged in DBMSs by conventional wisdom due to concerns about deadlocks and interrupt-handling overheads. In this demonstration, we highlight that this is no longer the case with PreemptDB, a modern memory-optimized DBMS that we built around (1) optimistic concurrency and (2) userspace interrupts that recently became available in x86 CPUs. PreemptDB proposes user-interruptassisted context switching to renew preemptive scheduling in modern DBMSs. Through a set of demonstration scenarios, we show that preemptive scheduling is practical and prioritizes high-priority transactions while preserving throughput and fairness.
Jiatang Zhou, Kaisong Huang, Zhuoyue Zhao 0001, Dong Xie 0001, Tianzheng Wang 0001
Proc. VLDB Endow.1