Score: 0

Revoke vs. Restart in Unweighted Throughput Scheduling

Published: October 16, 2025 | arXiv ID: 2510.15318v1

By: Changdao He

Potential Business Impact:

Makes computers finish jobs even when interrupted.

Business Areas:
Scheduling Information Technology, Software

We study the unweighted throughput scheduling problem on a single machine in the preemption-revoke model, where a running job may be aborted at any time, but all progress is permanently lost and the job cannot be restarted. Each job $J_i=(r_i,p_i,s_i)$ is defined by a release time $r_i$, a processing time $p_i$, and a slack $s_i$, and must start no later than $r_i+s_i$ to be feasible. We prove that no deterministic online algorithm can achieve a constant competitive ratio. The lower bound is established via an adversarial construction: starting from a three-job instance where $\textsf{ALG}$ completes at most one job while $\textsf{OPT}$ completes all three, we iteratively nest such constructions. By induction, for every $k\ge 3$, there exists an instance where $\textsf{ALG}$ completes at most one job, while $\textsf{OPT}$ completes at least $k$ jobs. Thus, the competitive ratio can be forced to $1/k$, and hence made arbitrarily close to zero. Our result stands in sharp contrast to the preemption-restart model, where Hoogeveen, Potts, and Woeginger (2000) gave a deterministic $1/2$-competitive algorithm.

Country of Origin
🇨🇦 Canada

Page Count
10 pages

Category
Computer Science:
Data Structures and Algorithms