Demo Data from EDBT 2026 / reviewers in the wild / expert
Nick Stanisha
dblp:299/4809
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2021
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Artificial intelligence and machine learning · 1 · 1 since 2021Databases, data management, data science and information retrieval · 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 |
Cloud and datacenter computing · 33% Electronic design automation · 33% Parallel and multicore computing · 33% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Cloud and datacenter computing
cluster resource management and scheduling |
0.5 | 1 | 2021 | Clockwork: A Delay-Based Global Scheduling Framework for More Consistent Landing Times in the Data Warehouse · KDD 2021 |
Parallel and multicore computing › parallel scheduling
list scheduling |
0.5 | 1 | 2021 | Clockwork: A Delay-Based Global Scheduling Framework for More Consistent Landing Times in the Data Warehouse · KDD 2021 |
Electronic design automation › high-level synthesis
scheduling |
0.5 | 1 | 2021 | Clockwork: A Delay-Based Global Scheduling Framework for More Consistent Landing Times in the Data Warehouse · KDD 2021 |
Methods — techniques the papers use, named apart from their topics
list scheduling · 0.5greedy procrastinating heuristic · 0.5
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2021 | Clockwork: A Delay-Based Global Scheduling Framework for More Consistent Landing Times in the Data WarehouseabstractRecurring batch data pipelines are a staple of the modern enterprise-scale data warehouse. As a data warehouse scales to support more products and services, a growing number of interdependent pipelines running at various cadences can give rise to periodic resource bottlenecks for the cluster. This resource contention results in pipelines starting at unpredictable times each day and consequently variable landing times for the data artifacts they produce. The variability gets compounded by the dependency structure of the workload, and the resulting unpredictability can disrupt the project workstreams which consume this data. We present Clockwork, a delay-based global scheduling framework for data pipelines which improves landing time stability by spreading out tasks throughout the day. Whereas most scheduling algorithms optimize for makespan or average job completion times, Clockwork's execution plan optimizes for stability in task completion times while also targeting predefined pipeline SLOs. We present this new problem formulation and design a list scheduling algorithm based on its analytic properties. We also discuss how we estimate the resource requirements for our recurring pipelines, and the architecture for integrating Clockwork with Dataswarm, Facebook's existing data workflow management service. Online experiments comparing this novel scheduling algorithm and a previously proposed greedy procrastinating heuristic show tasks complete almost an hour earlier on average, while exhibiting lower landing time variance and producing significantly less competition for resources in the cluster. Martin Valdez-Vivas, Nick Stanisha, Shan Li 0001, Luo Mi, Alex Kalinin, Josh Metzler |
KDD | 3 |